-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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 are showing up after updating to 0.54 #18165
Comments
Thanks for posting this! It looks like your issue may be incomplete. Are all the fields required by the Issue Template filled out? You may safely ignore this if you believe your issue contains all the relevant information. Thank you for your contributions. |
+1 Make release notes great again. |
I'm also receiving a lot of deprecation warnings. I think those are great to make libraries do the changes as early as possible. however not so great for the end user app dev experience ('cause RN show the yellow warning in the App itself.. maybe they should only be displayed in the console for so called "lowPriorityWarning"). Anyway, so if you are looking for a way to temporarily disable this as I am, I've figured you can do: require("ReactFeatureFlags").warnAboutDeprecatedLifecycles = false; |
For the list of deprecations you can probably already read https://medium.com/@baphemot/whats-new-in-react-16-3-d2c9b7b6193b and especially this RFC: https://github.com/reactjs/rfcs/blob/master/text/0006-static-lifecycle-methods.md |
@gre thanks dude! |
Hey, @gre! Where did you placed |
I answer my own question. Because require('ReactFeatureFlags').warnAboutDeprecatedLifecycles = false;
const {AppRegistry} = require('react-native');
const App = require('./App').default;
AppRegistry.registerComponent('iosapp', () => App); |
@DimitryDushkin I tried your fix but I am getting a weird error saying reducer is not a function:
Can you check it what's wrong with my require usage? |
@DimitryDushkin I have a separated file that I call polyfill.js, and in my entry point, i'll do |
@gre can you help me it's just very annoying. |
@sameer421 if you have @gre oh, that's clever :) |
@DimitryDushkin Thanks it worked. Removed All my warnings. |
in your AppRegistry file add an array of messages you want to ignore |
These warnings got into the release in this state by accident. It wasn't intentional. Please follow this thread: #18175 (comment). |
Since we updated to 0.54, we received a lot of deprecation warnings.
The reason that we updated was to address this issue. App works as expected, however, warnings are showing up.
Do we have a document or a website showing the full list of deprecations so we can act accordingly? Thank you!
The text was updated successfully, but these errors were encountered: