-
-
Notifications
You must be signed in to change notification settings - Fork 32.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
[Core] Remove style-propable mixin from transition-groups #2909
Conversation
Don't merge this by the way. Think we should iron out some syntax details mentioned in #2907 before doing mass conversion away from style-propable. |
Once #3124 is merged, we can start again this PR. |
Yup, I have a few branches that started this. Looking forward to picking this back up. I also have a local branch that takes all the components that are using |
8bf6114
to
d5fc7b4
Compare
@@ -91,8 +89,7 @@ const SlideIn = React.createClass({ | |||
|
|||
return ( | |||
<ReactTransitionGroup | |||
{...other} |
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.
Can we keep it?
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.
Thanks for the catch, that was not intentional 👍
I'm happy with it, I would say let's squash down and merge 🎉. |
This commit removes the `style-propable` mixin from `transition-groups` components. It replaces `this.mergeStyles()` with `Object.assign` and `this.prepareStyles()` with the same implementation that is stored in context. In addition, this commit replaces usage of `let` with `const` when the variable is not reassigned. Signed-off-by: Neil Gabbadon <[email protected]>
7467f54
to
91c12ea
Compare
Squashed here too! If all is green, feel free to merge 😄 |
@newoga Awesome, let's start the migration 🚜. |
[Core] Remove style-propable mixin from transition-groups
Yay, here we go! 🎉 🏃 |
I'm going to try my best to do this methodically.
Related to #2852.
Two of these components now no longer have mixins! Two of them use the PureRenderMixin. Do you think we should replace the PureRenderMixin with shallow-compare in preparation of moving these to classes?