Proposal: Persist Record Edit State when Edit Form Fails

[jimchamp]

Feature Request

Problem / Opportunity

Related to #9930

If a book page edit submission fails due to an unexpected error, the changes that were made are lost forever. It is extremely frustrating to editors when this happens.

Proposal

Instead of throwing away this work, let's improve the error handling/messaging and preserve the changes made by failed edits.

Breakdown

Related files

Refer to this map of common Endpoints:
*

Requirements Checklist

Checklist of requirements that need to be satisfied in order for this issue to be closed:

• [ ]

Stakeholders

• @tfmorris
• @seabelis
• @bilch
• @akramcodez

---

Instructions for Contributors

• Before creating a new branch or pushing up changes to a PR, please first run these commands to ensure your repository is up to date, as the pre-commit bot may add commits to your PRs upstream.

[Rishuraj2003-cmd]

Hi,
I went through the issue and understand that when an edit form submission fails,
the entered data is lost, which is frustrating for editors.

I’d like to help with this issue.
Before starting implementation, I wanted to ask:
– Is the preferred approach to persist the form state server-side (e.g. session)
or client-side (e.g. localStorage)?
– Are there any existing patterns in the codebase for handling failed form states?

Happy to help with a breakdown or small prototype if that’s useful.
Thanks!