For an application I’ve been working on, we’re building in issue-tracking features, similar to issues in GitHub / GitLab / etc. There’s an
issue type, and a
change-record type, where the client needs to provide edits to the issue and additional information that will only be part of the
This suggests that there’s a
change-request object type that’s POSTed to the server, but what’s created is a
change-record (with side effects on the
issue resource, all described in the
change-record resource that’s created).
It’s unclear to me whether this is a good way to model this, but it needs to be a single request for sane transaction management.
Is there a better or cleaner way to represent such an interaction with JSON:API?