| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Add the public Data Collection model, key-value collection behavior, and HTTP body direction types. Preserve unset values internally so the resolver can distinguish legacy bridge mode from explicit configuration. Refs #5666 Co-Authored-By: Claude <noreply@anthropic.com>
|
Sorry, something went wrong.
📲 Install BuildsAndroid
|
Sorry, something went wrong.
Performance metrics 🚀
|
Sorry, something went wrong.
Avoid coupling the Data Collection configuration test to reference identity. The test only needs to verify that setting a nested header behavior marks the configuration explicit. Refs #5666 Co-Authored-By: Claude <noreply@anthropic.com>
Remove the queue option from the initial Data Collection API because the Java SDK does not collect queue payload data that it could control. Co-Authored-By: Claude <noreply@anthropic.com>
Align the public Java API with the canonical Data Collection specification before release. The option has not shipped, so replace the old name without a compatibility alias. Refs #5666 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.
Rename the internal override marker to explain that it forces an empty Data Collection object into explicit mode. Align the related tests with the clarified semantics. Refs #5666 Co-Authored-By: Claude <noreply@anthropic.com>
| Back | FazBrowse Home | New Git URL |
PR Stack (Data Collection)
📜 Description
Add the foundational public types for configuring automatic data collection:
The public DataCollection() constructor represents an explicit object, including an explicit empty configuration. A package-private constructor supports the unconfigured instance that SentryOptions will own in the next stack PR. Mutable collection inputs are copied and exposed as immutable values.
This PR intentionally does not expose the model through SentryOptions or change runtime collection behavior.
💡 Motivation and Context
Establish the Java-shaped configuration model required by the Data Collection specification before adding resolution, configuration sources, and integration enforcement. Nullable raw values preserve the distinction between omitted values and explicit false or empty values.
Refs #5666
💚 How did you test it?
📝 Checklist
🔮 Next steps
Add the always-present DataCollection instance and resolver to SentryOptions, then wire external configuration and integrations in subsequent stack PRs.
#skip-changelog