-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use new audit IDs from graphql-http
for filtering acceptable warnings
#7338
Conversation
The latest minor in graphql-http adds unique and stable IDs for each audit. We can use these instead of substrings for explicitly filtering the audits we consider to be acceptable warnings.
✅ Deploy Preview for apollo-server-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit e40c098:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
heh, for what it's worth the old code was way more clear :)
but this will be more stable.
@glasser yeah, the comment is helpful though. Also I think this unlocks a pretty easy way for integrations to skip particular tests that don't make sense for them (like the fastify one)...though I obviously didn't implement that yet. |
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @apollo/server-integration-testsuite@4.3.3 ### Patch Changes - [#7338](#7338) [`01bc39838`](01bc398) Thanks [@trevor-scheer](https://github.com/trevor-scheer)! - Update graphql-http to 1.13.0 - Updated dependencies \[[`9de18b34c`](9de18b3), [`8c635d104`](8c635d1)]: - @apollo/server@4.3.3 ## @apollo/server@4.3.3 ### Patch Changes - [#7331](#7331) [`9de18b34c`](9de18b3) Thanks [@trevor-scheer](https://github.com/trevor-scheer)! - Unpin `node-abort-controller` and update to latest unbreaking patch - [#7136](#7136) [`8c635d104`](8c635d1) Thanks [@trevor-scheer](https://github.com/trevor-scheer)! - Errors reported by subgraphs (with no trace data in the response) are now accurately reflected in the numeric error stats. Operations that receive errors from subgraphs (with no trace data in the response) are no longer sent as incomplete, error-less traces. Note: in order for this fix to take effect, your `@apollo/gateway` version must be updated to v2.3.1 or later. Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@enisdenjo kindly implemented an off-the-cuff feature request that I made via graphql/graphql-http#49. Now we can filter our expected audit warnings in an explicit and stable way.