FIO-9921: fix issue with local paths not being propogated to edit grid #6072
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-9921
Description
Since we made changes to the way components' paths are stored and constructed, one crucial element of a correct path is the "local" flag, which determines whether or not a component should be pathed as "local" (i.e. to the current form context) or not (i.e. when it is participating in the process as a nested form).
This PR fixes an issue in EditGrid in which the local option was not being passed to a specific validation step. What's odd is that EditGrid appears to be the only component that calls the
invalidMessage
function and that validation step appears to be redundant, but for the sake of risk factor and incrementalism I've decided to just pass the option rather than taking the drastic step of removing the function call entirely.Breaking Changes / Backwards Compatibility
n/a
Dependencies
n/a
How has this PR been tested?
I couldn't figure out a way to reliably reproduce this issue in our automated testing because the only indication that something is wrong is a visual error (the form will successfully submit regardless of the validation problem). I'm going to investigate THAT issue (the fact that an invalid child form's parent will still successfully submit) and return to this to write tests.
Checklist: