Added system field "key" as optional argument for data object mutation #987
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 field "key" is a system field and should be treated the same way during both creation and updating. While it's possible to add the "key" field to the mutation configuration, this would mean that during creation, "key" would exist both as a parameter and a field on the input object, which can be confusing. In the update case, it would only be available as a field on the input object. Since "key" is required during creation, the parameter must be kept.