feat(#1352): add collection headers to introspection query #1353
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
reggermont
force-pushed
the
feature/add-collection-headers-to-introspection-query
branch
from
ff059f2 to
65f2858
Compare
reggermont
force-pushed
the
feature/add-collection-headers-to-introspection-query
branch
from
65f2858 to
a15ccef
Compare
|
Thanks for fixing this @reggermont ! This was a simple fix. My apologies for merging this late. |
|
My pleasure! You have your life, don't be sorry 😁 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Resolve #1352 by adding collection headers to the introspection query.
Considering a graphql api requiring mandatory headers defined in the collection headers, the introspection would currently fail.
For the same API:
Before:
After:
Contribution Checklist: