FIO-9515 Fixed Edit grid conditional values not displayed in Edit sub… #5988
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.
…mission
Link to Jira Ticket
https://formio.atlassian.net/browse/FIO-9515
Description
After changes to clearOnHide behavior, process of determining whether to clear the value of a component changed to the way so that when the form was initially loaded, component that were just rendered were compared with their own previous state, as if they were interacted with already, which is not a correct behavior. The check to see if the form is pristine was added, because clearOnHide function should not fire when the form is in fact pristine.
Added a condition so that we don't check each component visibility when the root is pristine, so that value can be deleted only on EditGrid data level when it is hidden/shown
Breaking Changes / Backwards Compatibility
Dependencies
How has this PR been tested?
Tested locally. All the tests for clearOnHide pass, so this is not a breaking change.
Checklist: