-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Optimization in use_reducer #3945
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
Open
Pascal-So
wants to merge
5
commits into
yewstack:master
Choose a base branch
from
Pascal-So:use_reducer_optimization
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
a0406ae
add failing test
Pascal-So d5d40bb
avoid rerender in use_reducer when Rc is reused
Pascal-So cff516e
add warning comment about assumptions
Pascal-So 11a4640
update use_reducer docs
Pascal-So 5e3dadf
move check to should_render_fn
Pascal-So File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
use_reducercurrently makes the explicit promise that "This hook will always trigger a re-render upon receiving an action". Please change the docs, as that's a breaking change. If you are reading this from the future and relying on this behaviour,use_force_updateprovides a hook to trigger this rerender manually.Since
use_reducer_baseis internal, could you push the changes to the callers into their respectiveshould_render_fnfor clarity inuse_reduceranduse_reducer_eqbelow?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.
Ah right, I updated the documentation accordingly.
As for moving the check into
should_render_fn, is the current version along the lines of what you meant? Now the base fn is completely unchanged from what it was before, the diff is only in theshould_render_fns