-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix forceUpdate edge cases #4048
Merged
marvinhagemeister
merged 1 commit into
preactjs:master
from
dmitrage:may-the-force-be-with-you
Jun 19, 2023
Merged
Fix forceUpdate edge cases #4048
marvinhagemeister
merged 1 commit into
preactjs:master
from
dmitrage:may-the-force-be-with-you
Jun 19, 2023
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
📊 Tachometer Benchmark ResultsSummaryduration
usedJSHeapSize
Results02_replace1k
duration
usedJSHeapSize
run-warmup-0
run-warmup-1
run-warmup-2
run-warmup-3
run-warmup-4
run-final
03_update10th1k_x16
duration
usedJSHeapSize
07_create10k
duration
usedJSHeapSize
filter_list
duration
usedJSHeapSize
hydrate1k
duration
usedJSHeapSize
many_updates
duration
usedJSHeapSize
text_update
duration
usedJSHeapSize
todo
duration
usedJSHeapSize
|
marvinhagemeister
approved these changes
Jun 19, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thank you so much for fixing this! This is a really well done PR ❤️
Merged
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.
For context: I use Preact with custom reactivity integration which makes heavy use of forceUpdate and shouldComponentUpdate.
While trying different approaches I've found two issues with
forceUpdate
and especially the_force
flag. Minimal test case is created for each._force
flag is reset afterrender
anddiffChildren
are completed. Example: parent component is forceUpdated during child component creation. In this case parent component is re-enqueued but at the time of re-rendering it will have_force
flag reset and because of thatshouldComponentUpdate
will be called while it should not. Resetting this flag before rendering resolves this issue._force
flag is ignored in strict-equality bail-out. Example: parent component caches render result to benefit from bail out, parent and child components are both forceUpdated. In this case bail out resets the_force
flag and child componentshouldComponentUpdate
is called while it should not. Not bailing out on forceUpdated components resolves this issue. But I'm afraid I miss the reason why it was allowed before.Workaround I use for both cases:
isForceUpdate
flag when callingforceUpdate