1131 variables in parse literal for Scalars #1170
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.
See #1131
This is useful for a Scalar implementation that wants to get access to the variables so they can do VariableReference AST replacement.
So for example
{ field (arg : { this: "ast can", variable : $replacement }
where arg is in fact defined as "a complete Scalar" and not a compound type
Passing the variables to parseLiteral is actually implemented in graphql-js.
An example of his in graphql-js is https://github.com/taion/graphql-type-json/blob/master/src/index.js#L36