fix(ui): significantly more predictable form state events #11597
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jacobsfletch
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, form state events are triggered by a debounced
useEffect. This, however, is very unpredictable and can lead to many bugs, including infinite loops (verified). Rather than relying on the rendering lifecycle and deep comparisons, we need to dispatch form state events declaratively.This change completely removes the reliance on a
useEffectin theFormcomponent and instead calls form state on demand through auseCallbackfunction. This change requires the removaluseReducerfor state management, and instead calls a reducer-like function directly.More details to come.