-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Try useAnimate for all <Animate /> cases, lightening the React tree #26201
Conversation
Size Change: -136 B (0%) Total Size: 1.19 MB
ℹ️ View Unchanged
|
@@ -27,9 +27,7 @@ function ComplementaryAreaSlot( { scope, ...props } ) { | |||
function ComplementaryAreaFill( { scope, children, className } ) { | |||
return ( | |||
<Fill name={ `ComplementaryArea/${ scope }` }> | |||
<Animate type="slide-in" options={ { origin: 'left' } }> | |||
{ () => <div className={ className }>{ children }</div> } |
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.
Class isn't used, so removing.
We can let it sit for a while as unstable and decide later. Not sure what the future is for these animation classes. Cc @jasmussen. In the mean time this makes some components less complex, especially the popover component. |
Thank you Ella. Also CC: @ItsJonQ |
Description
This hook was introduces (as unstable) in #26063, but it seems good to have for all instances where
<Animate />
is currently used. There's no good reason for this to be a component.Should we mark the hooks stable? Should we deprecate the component?
Should it remain in the
components
package? I think it still makes sense here since it provides a class, and it's mostly used in the package.How has this been tested?
Screenshots
Types of changes
Checklist: