docs(sentry-dio): improve addSentry
method documentation
#2912
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.
📜 Description
Improves the
addSentry()
method documentation in thesentry_dio
package with clearer usage examples and explanation.The updated docs now clearly explain that Sentry should be added as the last step in Dio configuration, ensuring that it uses the user's custom configuration rather than overriding it. Kudos to @ueman.
💡 Motivation and Context
When integrating Sentry with Dio, users need to understand the correct order of operations. Previously, the documentation didn't fully clarify that
addSentry()
should be called last after any custom transformer or adapter configuration. This led to confusion when users wanted to use custom Dio components alongside Sentry.This documentation improvement addresses the "Next steps" item from the previous PR that exported
SentryTransformer
, by explaining howaddSentry()
works with custom configurations.💚 How did you test it?
addSentry()
functions.📝 Checklist
sendDefaultPii
is enabled#skip-changelog