-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[docs] remove clientMutationId and Relay Mutation spec #2401
Conversation
Thank you Jan Kassens facebook/relay#2401
Now that #2349 finally landed, I think we're ready for this too! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kassens has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
Summary: 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. Pull Request resolved: #2401 Reviewed By: tyao1 Differential Revision: D18917450 Pulled By: kassens fbshipit-source-id: 4a5be749389872c62db6bde63e0c6b38f839b02c
I saw this in breaking changes for v8:
Will usages like |
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.