fix(form-core): #1182 remove stale form level validation errors. Main… #1186
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.
…tain cummulative errorMap instead of snapshot of previous validation cycle.
Problem
Currently, prevFieldsErrorMap, was being assigned to the current validation cycle's newErrorMap see here. This caused issues because when we run the validator we do not receive a value for fields with no errors. This meant that on subsequent validation cycles, when the error was cleared, our prevFieldsErrorMap did NOT have a value for the field thus not clearing the error when this loop executes.
Changes
Previously we would set prevFieldsErrorMap to an empty object if no fieldErrors on current cycle. With these changes now we set it to: