Skip to content

Is 'clientMutationId' needed anymore? #106

Open
@fiyazbinhasan

Description

@fiyazbinhasan

As of this pull request, facebook/relay@3838691

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requestedspec complianceThe change is intended to solve the problem of inconsistency with the official GraphQL specification

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions