-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Remove usage of unsafe lifecycle hooks (React 16.3) #553
Comments
There is a large rewrite required for 16.3. But the great news is that it will make Formik MUCH smaller, simplify tooling (microbundle), and no longer have prop-types as a peer dep. |
@jaredpalmer is the large rewrite you are talking about here PR #423 ? Where should we "track progress", on that PR, or elsewhere? |
Yes that was my first attempt. Just need time to finish it up. |
Hola! So here's the deal, between open source and my day job and life and what not, I have a lot to manage, so I use a GitHub bot to automate a few things here and there. This particular GitHub bot is going to mark this as stale because it has not had recent activity for a while. It will be closed if no further activity occurs in a few days. Do not take this personally--seriously--this is a completely automated action. If this is a mistake, just make a comment, DM me, send a carrier pidgeon, or a smoke signal. |
📌 |
Hola! So here's the deal, between open source and my day job and life and what not, I have a lot to manage, so I use a GitHub bot to automate a few things here and there. This particular GitHub bot is going to mark this as stale because it has not had recent activity for a while. It will be closed if no further activity occurs in a few days. Do not take this personally--seriously--this is a completely automated action. If this is a mistake, just make a comment, DM me, send a carrier pidgeon, or a smoke signal. |
📌 |
Bug, Feature, or Question?
Feature?
Current Behavior
Using Formik with React 16.3 with the
<React.StrictMode></React.StrictMode>
component will trigger some warnings.Desired Behavior
Different lifecycle hooks should be used.
Suggested Solutions
The warning message states:
The React team also made
react-lifecycles-compat
which should allow for backwards compatibility when using the new lifecycle hooks.Additional Information
More details are in the recent React blog post.
The text was updated successfully, but these errors were encountered: