Treat useStrictAccess
option as true by default
#700
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.
The
useStrictAccess
is a boolean option on GraphQL types. It istrue
by default. There is no need to render both states (true and false), so this PR changes it: it will be rendered only if set tofalse
. If it's not defined, it will be considered astrue
.Here is an example of an object type:
Obviously
'useStrictAccess' => true
is not needed here.Just a quick reminder: the
useStrictAccess
option is set tofalse
only if all the following conditions are met:access
option is setaccess
option is an expressionaccess
expression contains theobject
variable.