feat: Add provider to set additional sentry client options #46
Conversation
This file contains hidden or 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
paxuclus
approved these changes
Aug 20, 2025
stephanschuler
approved these changes
Aug 20, 2025
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Introduces an interface to get client options for sentry init and a base class to initialize sentry as before.
To use the object-management for getting an overwritten InitOptionsProvider, I had to move the initialization to a later step in the bootstrap sequence. It will now probably fail to capture errors earlier. Maybe there is a different step we could use or maybe it would be reasonable to just initialize with the base provider as before and initialize it again later?