bugfix: Honor directive imports when directive name is spec name #1720
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.
Currently, this import
is not honored. Specifically, elements marked
@inaccessible
will be removed, and elements marked@foo
will not be removed.This PR fixes the bug in
directiveNameInSchema()
that caused it, and adds a test for it.Thankfully, we currently don't generate
import
s in the supergraph schema. However, for the near future, we should avoid havingimport
s in the supergraph schema. If the desire arises to allowimport
s in the supergraph schema fromapollographql/federation
devs, please talk to Team Houston for next steps.