-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Refactored wrapper to load and wrap handler early #187
Merged
Merged
Changes from 14 commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
c8b40c9
chore: Updated agent for tests
mrickard 12e0500
fix: Refactored wrapper to wrap on load, to improve performance
mrickard bbe2fdd
chore: Refactored wrapper unit tests, to set env vars before the wrap…
mrickard 577c31e
chore: Refactored wrapper error-state unit tests, to set env vars bef…
mrickard 055597a
chore: Refactored wrapper error-state unit tests, so cjs is structure…
mrickard c733987
feat: Added callback-compatible wrapper
mrickard 3124af2
fix: Updated unit tests to set environment variables before wrapping
mrickard 99da90d
chore: Linted
mrickard 509c4c4
chore: Added unit tests for callback-supporting wrapper
mrickard 401f83f
chore: Removed callback-specific wrapper, and restored ESM async/CJS …
mrickard b209f2b
fix: Added async path for wrapping/returning ESM handler, and awaitin…
mrickard 8cc2df1
chore: Removed unneeded wrapper helper from build
mrickard 21dce74
chore(test): Changed rejects assertions to throws, and wrapped the ha…
mrickard a237fbc
chore(test): Changed rejects assertions to throws. Renamed ESM error-…
mrickard 5bc19db
chore: Updated package.json and lockfile
mrickard File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need a unit test for lambda in cjs with callback or are we just relying on the integration tests for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're relying on integration tests with the functions that return callbacks. For those, the issue hasn't been loss of instrumentation, but an interruption in the return value, so we test that explicitly for the callback-returning functions.