client-preset: allow skipDocumentsValidation in config #9653
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.
Description
Fixes a small issue raised in #8562
It appears that this line is necessary for
skipDocumentsValidation
to work when using theclient-preset
, as the setting is otherwise stripped out without being passed upstream.Type of change
Please delete options that are not relevant.
How Has This Been Tested?
I checked in a fixture that uses urql's
@populate
directive, which violates the ScalarLeafsRule validation rule.With the changes in this PR, I am able to successfully use the
skipDocumentsValidation
setting (as documented) to intentionally bypass this particular validation. Without the changes in this PR, the validation (that I asked to be skipped) will cause the codegen to fail when it is used alongside the client-preset.Checklist: