Require non-empty directive locations #4100
Merged
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.
A proposed spec edit clarifies a requirement that was always true but was slightly buried: directive definitions must include 1 or more locations.
This PR adds explicit validation to graphql-js around non-empty directive locations. Similar work was landed in graphql-java.
I'll add that I haven't contributed to graphql-js before and am not familiar with typescript or the mores of graphql-js. I've tried to follow existing patterns but would appreciate any feedback offered.