-
Notifications
You must be signed in to change notification settings - Fork 45
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
Generate a stable options object post-normalization #75
Closed
Closed
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 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.
Great catch
Unfortunately it won't work if values are updated, which may be the case because some options are callbacks and users might provide inlined arrow functions
I suggest using the
useGetter()
hook above to solve this more reliably once for all(also worth applying to other methods as well, we don't follow the rules of hooks very strictly 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.
Right, this still isn't stable if anon callbacks are passed, but it at least handles the case of empty options being passed (a potentially common use case).
Thanks for linking to your issue on useGetter in the code. It was fascinating to see other lib/hook authors face these changes. I don't want to pull the argument over here, but my read on the responses is that the
useGetter
pattern is pretty dangerous to use. In my limited experience, I've gone to great lengths to keep callbacks stable and I've documented to users what they are responsible for memoizing. It's an uphill battle and we need help from React core to make it easier, but I feel it's the safest solution in userland.I don't feel comfortable updating to
useGetter
. If you'd like this PR as is, go ahead and merge it. Otherwise, I recommend closing it out or commandeering.