fix(core): update client options to allow explicit undefined
#18024
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.
Before submitting a pull request, please take a look at our
Contributing guidelines and verify:
If you've added code that should be tested, please add tests.Ensure your code lints and the test suite passes (.yarn lint) & (yarn test)Currently with
exactOptionalPropertyTypesenabled (which is now the default for new TS projects) doing something like this is not allowed:as while
undefinedis supported, the types don't allow it as an explicit value.It looks like this has come up before and Sentry is wanting to support it, though I'm not sure what ended up happening because the end ticket got closed without any associated PR.
I've purposely just opened this updating the client option properties that I think this feature is most commonly used with