Support validation against multiple schemas. #31
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.
This is a backwards-compatible change which supports multiple option groups being passed in. Tags must be unique and can refer to different schemas.
This is useful for codebases that interact with multiple GraphQL endpoints. In our case, we have multiple backend services exposing their own GraphQL schemas, and this allows us to lint their usage via backend-specific tags.
For example:
via the configuration:
If #26 and #28 can be merged in first, I'd be happy to rebase this against those changes.