| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Control GraphQL documents and variables through the new Data Collection policies across GraphQL and Apollo integrations. Preserve sendDefaultPii and maxRequestBodySize behavior when Data Collection is absent. Co-Authored-By: Claude <noreply@anthropic.com>
|
Sorry, something went wrong.
📲 Install BuildsAndroid
|
Sorry, something went wrong.
Bring the queue option removal and preceding stack updates into this layer.
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.
Add focused coverage for parsing a single GraphQL request object and independently removing document and variable content while preserving operation metadata and allowed fields. Refs #5666 Co-Authored-By: Claude <noreply@anthropic.com>
Apply document and variable collection policies to every operation in a batched GraphQL request. Fail closed when a batch contains non-object entries instead of attaching partially filtered content. Refs #5666 Co-Authored-By: Claude <noreply@anthropic.com>
Verify GraphQL request filtering fails closed when a batch contains a non-object entry. Refs #5666 Co-Authored-By: Claude <noreply@anthropic.com>
Performance metrics 🚀
Previous results on branch: feat/data-collection-graphqlStartup times
App size
|
Sorry, something went wrong.
…n-graphql # Conflicts: # sentry/src/test/java/io/sentry/DataCollectionResolverTest.kt
There was a problem hiding this comment.
LGTM 👍
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Stack (Data Collection)
📜 Description
Apply Data Collection policies to GraphQL document and variable capture across GraphQL Java and Apollo 2, 3, and 4 integrations.
The integrations independently filter GraphQL documents and variables while retaining operation metadata. Legacy sendDefaultPii, request-size, and integration-specific always-collect behavior remain unchanged when Data Collection is absent.
💡 Motivation and Context
GraphQL documents and variables can contain customer data. The new namespace provides granular control without forcing integrations to interpret legacy options themselves.
Refs #5666
💚 How did you test it?
📝 Checklist
🔮 Next steps
Apply the remaining Data Collection categories to database and HTTP integration paths.
#skip-changelog