| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Use the Data Collection incoming response body decision when attaching failed GraphQL response content in Apollo 3 and 4. Continue reading responses for error detection and retain status and body size metadata. Co-Authored-By: Claude <noreply@anthropic.com>
|
Sorry, something went wrong.
📲 Install BuildsAndroid
|
Sorry, something went wrong.
Performance metrics 🚀
Baseline results on branch: feat/data-collection-incoming-request-bodyStartup times
App size
|
Sorry, something went wrong.
Bring the queue option removal and preceding stack updates into this layer.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
…ata-collection-incoming-response-body
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.
…ata-collection-incoming-response-body
…ata-collection-incoming-response-body
…ata-collection-incoming-response-body
…ata-collection-incoming-response-body
| Back | FazBrowse Home | New Git URL |
PR Stack (Data Collection)
📜 Description
Apply the incoming response body policy to Apollo 3 and Apollo 4 failed GraphQL events.
When disabled, response body content is omitted while status code and body size remain attached. Existing always-collect behavior remains unchanged when Data Collection is absent.
💡 Motivation and Context
Apollo operates as an HTTP client, so received GraphQL response content maps to the incoming response body direction and should be independently configurable.
Refs #5666
💚 How did you test it?
📝 Checklist
🔮 Next steps
Apply outgoing request and server response body policies.
#skip-changelog