-
Notifications
You must be signed in to change notification settings - Fork 3.9k
fix: [patch react-native-modal] update backdrop animation in strict mode #46830
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
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
2431437
fix: [patch react-native-modal] update backdrop animation in strict mode
dominictb 5e010d7
Merge remote-tracking branch 'origin/main' into fix/45385-modal-stric…
dominictb f48b542
fix: group setState ops to avoid extra nested updates in React
dominictb 692de92
Merge remote-tracking branch 'origin/main' into fix/45385-modal-stric…
dominictb 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
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.
I'm not sure why you are storing the opacity value which comes from props into state. Why can't you just use it directly from props?
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.
@allroundexperts we need to save both the prevOpacity and opacity of the backdrop, because sometime (for example
onPanResponderMove, you might want to animate to a different opacity thanprops.backdropOpacity. And obviously we need to save the prevOpacity in order to build the correct animation for the backdrop. Hence this implementation.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.
That's fine. But instead of saving it in the state, can't you just use the
usePrevioushook? It would store the previous value in a ref which will prevent additional renders.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.
react-native-modalis written in class component style.this.setStatecall, and it already passed the performance test. Also, it's a bit overkill to get something likeusePreviousin this class component.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, makes sense. I did not consider that this was a class component.