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:
[x] I have completed the above PR template
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (if applicable)
[x] My changes generate no new warnings
[x] My changes include tests that prove my fix is effective (or that my feature works as intended)
[x] New and existing unit/integration tests pass locally with my changes
[ ] Any dependent changes have corresponding PRs that are listed above
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: