Standardise return values for GraphQL destroy mutations

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

What is our standard for a successful destroy mutation?

• The object just destroyed
• The remaining objects in the collection
• nil
• something else?

The following discussion from !40930 (merged) should be addressed:

• @alexkalderimis started a discussion: (+12 comments)

  is there any data we can return alongside the errors that clients would find useful (to avoid a second follow-up request to update the client state)?

  Perhaps this mutation should have a boards field?