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.
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
Small logic cleanups #3451
Small logic cleanups #3451
Changes from 5 commits
d7c7cab
7af74dc
deb4b27
121840c
c9831f9
e98ebae
84d5ceb
8dfc085
bebdc8f
4042122
9f706f0
082d63d
ef11e61
7982c8f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Calling this
onCloseAnimationComplete
I think gives us a better sense of the purpose of this function. Too many things calledclose
andonClose
gets a bit confusing I think.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.
To expand on why this is necessary:
On some lower end devices, if we try to do all of this at the same time as
sheet.current?.close()
, there is a significant performance drop. On Android, I can make the FPS drop to zero just by closing the sheet and removing a post from the feed at the same time.Instead, we want to call
sheet.current?.close()
, and let theBottomSheet
component decide when to callonCloseAnimationComplete
, ensuring a smooth transition.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.
isVisible
has a default value oftrue
and here we never actually would have changed this tofalse
.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 also can't see a visual difference after removing this in the web version, so unsure if we need it. We're conditionally rendering in the dialog once
isOpen
changes to true, so we still get theAnimated.View
entering
animations.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.
State calls during events should be batched so I'm not sure there'd be a difference either way.
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.
Oh ya know what, this is leftovers from an exit animation we removed, def safe to remove