FIO-7808: fixed an issue where conditional editGrid loses the value after submission #5511
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.
Link to Jira Ticket
https://formio.atlassian.net/browse/FIO-7808
Description
What changed?
When the validator is run on the server side, the server option is passed for the form and the setValue is called.
When the server option is passed, the clearOnHide method unsets the components values once the conditions check defines that the component is not conditionally visible. The setValue method of editGrid can potentially trigger the conditions check 4 times and it can appear that the values are unset for the editGrid before the other form values are set and the conditions check on the form level is triggered . This PR allows only the conditions check that comes from the form level for the hidden editGrid with server option.
Why have you chosen this solution?
Since this kind of issue is reported for editGrid component only and related to its server behavior, i was trying to make my changes closely specific to editGrid and server option, not to break other components and use cases.
How has this PR been tested?
Formiojs and formio-server tests with those changes are passed for me locally.
I have added automated tests for all use cases where I was able to see the similar issue.
Checklist: