This repository has been archived by the owner on Sep 3, 2021. It is now read-only.
Experimental mutation API: Fixes for data input objects #536
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.
This PR fixes some issues in the initial implementation of the experimental node mutation API introduced in #531. Given a
User
node type, the_UserData
input object generated for thedata
argument ofCreate
,Merge
, andUpdate
mutations was failing to preserve list type wrappers and nullability. So,Create
andMerge
now use a new_UserCreate
input object, which preserves nullability andUpdate
uses a_UserUpdate
input object that keeps arguments optional. In both cases, list type wrappers are preserved, appropriately allowing for list arguments.Docs update: https://deploy-preview-60--distracted-golick-08ed24.netlify.app/docs/graphql-schema-generation-augmentation#experimental-api