FIO-8273 fixed advanced logic for data components #211
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-8273
Description
Fixed the behavior when the properties of the original component changed when the logic was triggered, which led to a change in all nested components inside the Data components
Previously If the logic was triggered, then the properties of the original component changed. For example, there is a DataGrid component in the form. Inside the DataGrid component, there is a Text Field component with logic, when triggered, the required property for the textField component is added. For the DataGrid Component, the evaluate Process is executed row by row. Therefore, if validate.required = true is set in any row for TextField after triggering the logic, then this property changes the original component and is applied to all following TextField rows. This issue has been fixed by cloning the original component.
Breaking Changes / Backwards Compatibility
n/a
Dependencies
n/a
How has this PR been tested?
Automated tests have been added. All tests pass locally
Checklist: