96037069ff
Before, when autosaving a draft, removing a repetition row would send `_destroy` inputs to the controller – but not remove the row from the DOM. This led to the `_destroy` inputs being sent again on the next autosave request, which made the controller raise (because the row fields were already deleted before). To fix this, we let the controller response remove the deleted row(s) from the DOM. Doing it using a controller response avoids the need to keep track of operations on the Javascript side: the controller can easily know which row was just deleted, and emit the relevant changes for the DOM. This keeps the autosave requests robust: even if a request is skipped (e.g. because of a network interruption), the next request will still contain the relevant informations to succeed, and not let the form in an unstable state. Fix #5470 |
||
|---|---|---|
| .. | ||
| activate | ||
| confirmations | ||
| demarches | ||
| dossiers | ||
| feedbacks | ||
| passwords | ||
| profil | ||
| registrations | ||
| sessions | ||
| shared | ||
| _general_footer_row.html.haml | ||
| _login_banner.html.haml | ||
| _procedure_footer.html.haml | ||