-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Deprecation warnings with React 15.5.3 #1661
Comments
@JedWatson : i see a open PR #1658 . Can you please merge into master. I just updated my react version and started getting errors in console. (I see that travis build has failed on that PR but i am sure that would be a 1 min fix) Looking forward to a merge and version upgrade. Thanks |
Facing same issue! Looking forward to a merge and version upgrade. |
Same issue. When to expect this fix? |
Please! |
Please fix the new deprecation warnings from fb-react |
I also would love to see this updated as well. I'm a little worried that there haven't been any new commits in over a month. |
These are fixed with #1658 and are now released 🙂 |
Updated and everything works fine for me. Thank you once again for this great package. |
…sses warnings Summary: With React-Dom@15.5.0 we are getting warnings React.createClass is deprecated. We are not using react.createClass in our code-base but some of the dependancies react-bootstrap, react-select use react.createClass and have PR's regarding the same have not been yet been resolved. JedWatson/react-select#1661 Hence keeping to React, React-Dom versions 15.4.0 until the PR's for React-Bootstrap and React-Select are resolved. Test Plan: Go to browser console. You should not see any console warnings. Reviewers: karthik, jeff, ram Reviewed By: ram Subscribers: jenkins-bot, ui, yugaware Differential Revision: https://phabricator.dev.yugabyte.com/D1890
Solution for first one:
Not sure about the exact fix for the second one. I guess adding create-react-class to dependencies if refactoring to classes isn't viable?
Thanks for building this package, dude!
The text was updated successfully, but these errors were encountered: