Avoid unnecessary re-renders by comparing errors to previous errors #2069
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.
This addresses part of #1974
Each time any field is touched (onChange, onBlur) the errors on the context changed, causing all fields to re-render once more than needed (2 renders per change)
This fix will compare the new errors object being assigned to the existing one, and only change the state if they are different.
FastField is still fundamentally broken, because it will re-render on each change to the context. Should be fixed in #2070