-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
[Ripple] Use custom transition logic #16525
Conversation
Details of bundle changes.Comparing: 2cceffb...5499a0d
|
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.
👌
Co-Authored-By: Olivier Tassinari <[email protected]>
I wish we were tracking the bundle size of the Button. I'm sure this has helped :) |
|
Oh yes, we do! I was expecting to see the diff in the summary :), well done. |
Review per-commit is advised.
Reduces implementation logic (remove unused
className
and enter delay). We only ever needed the exit transition for which we don't need a complete Transition component. This makesRipple
StrictMode compatible which cascades to a lot of components since ButtonBase only usesTransitionGroup
which is StrictMode compatible as ofreact-transition-group@^4.0.0
.Also reduces the number of commits (no more
enter
transition which was never needed as far as I can tell).