graphql-dotnet / graphql-dotnet/relay
Is 'clientMutationId' needed anymore?
- Dominant language
- C#
- Stars
- 74
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
As of this pull request, https://github.com/facebook/relay/commit/3838691f4f815ce90b6d544fa052b112259a4c9a
RelayModern has no requirements on mutations beyond the general mutation specs. Specifically, the additional requirements that are no longer required are:
- `clientMutationId` (even RelayClassic only required this because of FB internal reasons)
- `$input` objects, with RelayModern the input to mutations can come either as one big object or multiple mutation arguments.
As clientMutationId is no longer needed in RelayModern, we can remove the `MutationInputGraphType` altogether. Instead, we can use the actual `InputGraphType`. Do you guys agree?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.