-
Notifications
You must be signed in to change notification settings - Fork 149
Memoize hook output #149
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
Merged
hartzis
merged 2 commits into
FormidableLabs:master
from
FaberVitale:memoize-hook-output
Jun 15, 2019
Merged
Memoize hook output #149
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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.
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.
💡 Thoughts on memoizing the class component?
Could add
handlers
andattachTouch
tothis
and set in the constructor initially, and add acomponentDidUpdate
that only re-runsgetHandlers
iftrackMouse
changes?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.
It should work flawlessly.
Let me try implement this enhancement:
if it works, I'll push the changes here.
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.
Cache handlers
We should use
getDerivedStateFromProps
instead ofcomponentDidUpdate
to preservethe same order of operations between the hook version and the component version:
componentDidUpdate
runs in the commit phase while all theuseSwipeable
code runs in the render phase(see).Here's a snippet:
SSR
We should add 1 or 2 SSR tests but I think it is outside the scope of this pull request.
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.
Pushed a version that uses getDerivedStateFromProps in this branch.
I've noticed that this packages has React >= 16.0.0 as peerDependency but
getDerivedStateFromProps
got added in v16.3.You'd probably have to bump to a major version if you want to either use getDerivedStateFromProps
or move the logic of both hook and component logic from the render phase to the commit one.
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.
I agree with
getDerivedStatefromProps
and really like your implementation.Release a major to include the class-based improvements is definitely the right way along with bumping the required minimum version of react.
With your guidance and example implementation, I think I'm leaning towards holding off, possibly indefinitely, on the including the class-based improvements. As hooks are the path forward I think the next major of this package should probably deprecate the component and only export a hook.
Let's just move forward with this amazing addition to the hook! Thank you @FaberVitale!