FIO-9308: Fixed the paths with nested forms by ensuring we are always dealing with the absolute paths with clearOnHide, conditions, filters, and validations. #187
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-9308
https://formio.atlassian.net/browse/FIO-9306
Description
There are many places within the core processors, where the "absolute" path is needed to determine which fields are modified via the conditionals, clear on hide, etc. The problem is with Nested Forms, the "path" is relative and is not absolute. To fix this issue, we need to make a call to "getAbsoluteComponentPath" which ensures we are dealing with the absolute paths when making these decisions.
Breaking Changes / Backwards Compatibility
None
Dependencies
How has this PR been tested?
Automated tests was written for the 9308 failure.
Checklist: