Fix async validation errors persist when unrelated fields are edited #3549
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.
Fixes #3536
Changes:
Removed validateFields prop from username and email fields in SignupForm.jsx to ensure async validation errors persist when other fields change.
Updated validateSignup function in reduxFormUtils.js to merge existing async errors with synchronous validations to prevent overwriting error messages prematurely.
Verified that username and email validation errors no longer disappear when editing unrelated fields such as password or confirmPassword.
Tested locally with multiple validation scenarios; all errors behave as expected.
Ensured change complies with existing linting and testing standards.
Checklist:
has no linting errors (npm run lint)
has no test errors (npm run test)
is from a uniquely-named feature branch and is up to date with the develop branch
is descriptively named and links to an issue number, i.e. Fixes #123