fix(stitching): avoid duplicate directives #1665
Merged
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
Fixes #1656. Later directives with the same name should override earlier directives rather than causing an error. Directives with the same names from a later subschema will override an earlier subschema. Directives from typedefs will override both. Mixing of legacy schemas argument and newer subschemas, typeDefs, and types arguments should respect this same order. We can consider adding onDirectiveConflict option to match onTypeConflict for customization.
|
The latest changes of this PR are available as alpha in npm: Quickly update your package.json by running: |
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.
Fixes #1656.
Later directives with the same name should override earlier directives rather than causing an error.
Directives with the same names from a later subschema will override an earlier subschema. Directives from typedefs will override both.
Mixing of legacy schemas argument and newer subschemas, typeDefs, and types arguments should respect this same order.
We can consider adding onDirectiveConflict option to match onTypeConflict for customization.