Remove unnecessary failed save form data session handling #1198
+0
−124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes the in-session handling of form data that previously caused server-side errors.
The issue was as follows: when a server-side error occurred while saving an object, the problematic form was displayed after showing the error message. However, upon reloading the object detail page, the form still displayed the erroneous data rather than the current data from the database, as expected. A second reload was required to display the correct data.
Since saving errors are now managed via AJAX, it’s no longer necessary to retain the erroneous data on reload. The in-session handling has therefore been removed.