fix(cloudflare)!: add better type handling for additional context #15276
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.
What/Why?
Adds better handling of Cloudflare context for types. Using
any
andunknown
in an interface was causing type mismatch, so even though it's more verbose, we should match the types needed from Cloudflare:Noticed a v9 is coming soon, so thought it's a good opportunity to add a BC now.
BREAKING CHANGE:
Updates the cloudflare withSentry handler generic type to allow passing in additional types used by ExportedHandler.
Before:
After:
Before submitting a pull request, please take a look at our
Contributing guidelines and verify:
yarn lint
) & (yarn test
).