Add support for custom selection of validators. #34
Conversation
This file contains hidden or 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
The LoneAnonymousOperation and NoUnusedFragments validation errors may not contain a location.
Nothing in the test schema was non-nullable, which prevented tests against nullability validators.
|
Looks great, thank you! If you have time can you see if updating to the newest |
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.
This adds support for configurable selection of GraphQL validators.
The addition is fully backwards-compatible for configurations that specified a value for
env.For configurations that did not set
env, all validators are now enabled by default. This is a slight change becauseKnownFragmentNamesandNoUnusedFragmentshad been disabled entirely for reasons that appear specific to Lokka.Resolves #10