-
Notifications
You must be signed in to change notification settings - Fork 148
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
Change architecture for functional components #808
Comments
@pauloreis7 Thank you for opening the discussion. I agree that the code base should be modernized and optimized. Is this something you would want to contribute to? |
I'd love to try this. |
Can I use TS + React hooks? |
Sure TS and hooks are a good foundation. Just ensure all existing tests pass as you refactor. |
ok, probably today i'll get start. |
The current project is using react components written in class form, which is already outdated and it is no longer advisable to write components this way. You can see more about it in this link.
Changing components written in class to function format is a very important update to bring scalability, best practices and simpler refactoring to the project.
So that future people in the community who want to contribute, but don't know this old format of creating react components, can also add to react-stickynode.
Surely this is an important change for the future of the project in all aspects.
The text was updated successfully, but these errors were encountered: