This is a tracker for all the issues relating to improving the experience of using mutations.

Proposed Work

The most of this can be solved holistically is through a refactor of mutations to support functionality more uniformly. The first step is to decide whether to implement a new Model layer or abstract class (see #143).

Other items can be done independently, but might make more sense to wait until the refactor is complete so as to reduce duplicate work.

• Refactor Mutations
  • #143
  • #379
  • Hook parity between mutations, and covering parts of the mutation $config not included in WPObjectType
    ( e.g. #1429, #965 )
  • Add more informative fields to the payload when permissions prevent the user from seeing the mutated object
    (e.g. #2100, #1839)
• Add new mutations
  • #2170
  • #181
  • #180
  • #1200
• API: add deregister_graphql_mutation()
  (#874, #1733)
• Bugfix: #807
• Tests: #2456

If I missed an issue or if you have a use case not referenced by an existing issue, please share and I'll add it to the tracker.