fix: prevent fetcher formData race condition in optimistic UI (#14506) #14612
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.
Description
Fixes a race condition where
fetcher.formDatabecomesundefinedbefore navigationloaderDatais available, causing UI flicker in optimistic update patterns.Problem
The issue occurred because fetchers transitioned to idle state in
processLoaderDatabefore the navigation'sloaderDatawas committed incompleteNavigation. This created a gap where bothformDataand updatedloaderDatawere unavailable, causing the UI to briefly show stale data.Solution
formDatapreserved until navigation completesloaderDataupdates incompleteNavigationChanges
processLoaderDatato preserve fetcher loading state during navigationcompleteNavigationto handle fetcher state transitions atomicallyTesting
true -> true -> true(no flicker). Previously would have showntrue -> false -> true(flicker)Fixes #14506