Skip to content

Make it clearer when endpoints modify the entity they're saving #64554

@dsas

Description

@dsas

What problem does this address?

When saving an entity in Gutenberg it sends the entity being saved to the server, and the server responds with what it actually saved. Gutenberg then applies the saved version to its state.

I've experienced multiple problems where a bug, both in Gutenberg and in our own code have meant that the server replies back with something different different than was requested - usually something missing. These issues are can be a pain to track down and also be rather subtle. I'd like this to be easier.

Here's a list of some example bugs which might have been easier to find and fix:

What is your proposed solution?

It'd be helpful in diagnosing these bugs if there was a log that something was different. Ideally some kind of diff, but at the minimum a log message saying something like "Content in server response differs from request".

Metadata

Metadata

Assignees

No one assigned

    Labels

    No fields configured for Enhancement.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions