-
Notifications
You must be signed in to change notification settings - Fork 46
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
Any plans on moving to hooks? #908
Comments
We will probably move to hooks here 😉 We already use them in production 👼 But regarding the strategy, I don't really see the point to rewrite everything in hooks style (since the library API is the same) However it can be nice to have a hook version of our context component (to avoid nestead render props 😄 ) So let's begin by @adeelibr Are you interest to take this feature? |
@fabien0102 I like your idea. Let's queue this for v14 as it will be a great breaking change. Step 1 is to update the |
@adeelibr, to add to @fabien0102's great answer to your question, here's a nice todo list if you're interested in contributing: #908 I'd suggest discussing further there. Please close this issue if you agree, or feel free to carry on the conversation here. |
I would love to 👍 @fabien0102
|
Oops, I meant #910 😂 |
Great! I am closing this issue in favor of #910, I'd like to start of working with |
With hooks coming out of alpha version soon, is there a road map in place to move/migrate all Class components to hooks. With hooks everything is a function.
The text was updated successfully, but these errors were encountered: