-
-
Notifications
You must be signed in to change notification settings - Fork 298
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
Migrate from React.PropTypes to prop-types #325
Comments
Hi, I think this is due to the next react upgrade. React.PropTypes will be deprecated and replaced by a standalone package prop-types. You can find the deprecation notice on the react documentation page. To sum up
|
hi, |
We can simply wait for @mlaursen to fix it. The warning is not serious right now, your app will work fine. |
@leedstyh just spent some time playing with the components. They seem to be working fine |
Yeah, I'm a little unsure about how to handle this migration. I'll need to wait for react-motion to update and also figure out what the new convention for the |
With the React 15.5 changes, moved the PropTypes from the main package to prop-types. References #325
Merged over from react-addons-css-transition-group and react-addons-transition-group to the new react-transition-group package. References #325
Hi, when will these changed be merged with the main branch? Currently my Jest snapshot tests are not working because of this. Please take your time, I don't mean to be impatient, it's just for planning ahead. 😄 |
Right now, I am unable to merge due to this bug in the new react-transition-group. Once it has been fixed, I'll do a patch with this changes as well. So hopefully really soon! |
Thanks for the information! |
Hi, I'm gettting this errors
Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead.
Warning: Motion: React.createClass is deprecated and will be removed in version 16. Use plain JavaScript classes instead. If you're not yet ready to migrate, create-react-class is available on npm as a drop-in replacement.
How can I fix them?
The text was updated successfully, but these errors were encountered: