Change
Refactor form change detection
Issue description
Currently form changes are recognized and tracked individually. It would be better to compute the form state (a query string) initially, and then later recompute the form state and compare it to intially computed one. This would make it easier to decide whether or not there are changes independent of how the initial form state was created, e.g. via prefill over the URL or a local backup. This would also cover cases where a user changes a prefill to different value and then back to the prefilled value, which then means no change.
Developer comments
As a consequence, creating an adjunct or option in a child form is no longer considered a change unless at least one field was completed therein. This is acceptable, as the user up to this point only said "And one more thing …".
|
Work sessions
Start |
2022-06-10T10:25:54
|
End |
2022-06-10T11:51:08
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.