print mutation variables besides $input #344
Closed
+217
−70
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.
Addresses #307 - We currently assume that mutations have exactly one variable
$input
- however, tracked queries may contain fields with calls that have Enum/InputObject types. These call values must also be printed as variables.Changes:
preset
argument toprofilePicture
that accepts an Enum value, as a way of testing call variables in tracked queriesRelayMutationQuery
to accept the value of$input
as a param and pass it through toRelayQuery.Node.buildMutation
RelayMutationRequest
to return the variables from the printer instead of hard-coding to$input