-
Notifications
You must be signed in to change notification settings - Fork 477
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
🚀 - Migrate Demo
components to the new API
page approach
#9057
Comments
We would also need to add dropdown controls and textfield controls similarly to appearance as reusable pieces of docs. |
Need to fix #9206 |
We need this in |
Hi @waterplea & @splincode, This issue appears to be of higher priority and requires more effort than #8982 and other open issues. I'd appreciate your suggestions on whether to focus on this or prioritize other issues based on the upcoming release planning. |
@shiv9604 you can pick components one by one and migrate them to the new API components. Just don't take any from the legacy package. That would be very helpful, thank you! |
Sure @waterplea. Thanks for your suggestion! |
Co-authored-by: taiga-family-bot <[email protected]>
…0108) Co-authored-by: Максим Иванов <[email protected]>
Co-authored-by: Максим Иванов <[email protected]>
Description
Migrate other
Demo
components to the newAPI
page approach as in tuiBlockShould be visible main properties, appearances and icons
The text was updated successfully, but these errors were encountered: