-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
Rewrite Class-Based React Components to Functional Components in Modelina Website #1648
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
Can you assign this issue to me? |
Hi @asv018, I Have already started working on this. If you are interested in contributing, I can recommend you some other issues. |
Yeah sure |
I can also work upon this issue. |
It will be good if you can assign this issue to me. I am also starting contributing to it. |
🎉 This issue has been resolved in version 2.0.11 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 3.0.0-next.8 🎉 The release is available on: Your semantic-release bot 📦🚀 |
The current codebase of the Playground Generator Options, Docs, and Examples Components of the Modelina Website contains class-based react components. We should update the code base to use functional components and hooks at all places. This will result in cleaner, easier-to-understand components compared to class components. This issue is to track my work on this.
The text was updated successfully, but these errors were encountered: