API design choice: nested mutations vs per-entity mutations

[me-andre]

Description

As a developer I want predictable and consistent API design So that I can create reusable client forms for common things

Acceptance criteria

• [ ] If something is updated as part of other thing, there's no ID needed for the nested one
• [ ] If ID is needed for that something, it should not be part of other BigThingUpdateInput type, but rather an updatable things on its own, so that we can create self-enclosed components that manage various types (References, Tagsets etc)

Additional Context

Screen shots / UX designs / data that are relevant.

Areas that will be affected

To be added during the refinement