| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Add an always-present DataCollection object to SentryOptions while preserving an unconfigured state for the legacy bridge. Expose public getter and setter APIs and cover explicit-empty and nested override behavior. Refs #5666 Co-Authored-By: Claude <noreply@anthropic.com>
|
Sorry, something went wrong.
📲 Install BuildsAndroid
|
Sorry, something went wrong.
Performance metrics 🚀
Previous results on branch: feat/data-collection-optionsStartup times
App size
|
Sorry, something went wrong.
Bring the queue option removal from the foundation branch into the SentryOptions layer.
Use the supported user information option to verify that SentryOptions replaces its Data Collection instance. Co-Authored-By: Claude <noreply@anthropic.com>
Semver Impact of This PR🟡 Minor (new features) 📋 Changelog PreviewThis is how your changes will appear in the changelog. This PR will not appear in the changelog. 🤖 This preview updates automatically when you update the PR. |
Sorry, something went wrong.
Ignore null assignments so the always-present Data Collection configuration and its current values remain intact. Refs #5666 Co-Authored-By: Claude <noreply@anthropic.com>
| Back | FazBrowse Home | New Git URL |
PR Stack (Data Collection)
📜 Description
Expose the Data Collection configuration model through SentryOptions:
This PR only exposes and stores the configuration. It does not resolve effective policies or change runtime collection behavior.
💡 Motivation and Context
Customers need a non-null, mutable configuration object so individual data-collection categories can be configured without first constructing the namespace. At the same time, the SDK must distinguish users who did not configure Data Collection from users who explicitly supplied an empty object and opted into the specification defaults.
Refs #5666
💚 How did you test it?
📝 Checklist
🔮 Next steps
Add centralized policy resolution and the legacy sendDefaultPii compatibility bridge, then wire configuration sources and integrations in subsequent stack PRs.
#skip-changelog