Add Input/Output model splitting to GraphQL mutation engine #60
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.
Summary
This PR adds usage-aware model mutations that create separate input and output type variants based on how models are used in operations. This brings the TSP models in line with the GraphQL requirement of separate input and output types.
Changes
GraphQLMutationOptions- AddedusageFlagandmutationKeyfor usage-aware cachingGraphQLModelMutation- Adds "Input" suffix for input typesGraphQLMutationEngine.mutateModel()- ReturnsModelMutationResultwith separate input/output mutationsModelTypeMap- SupportsGraphQLInputObjectTypefor input typesHow it works