Skip to content
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

Open
mdlufy opened this issue Sep 17, 2024 · 6 comments · Fixed by #10079, #10081, #10083, #10108 or #10112
Open

🚀 - Migrate Demo components to the new API page approach #9057

mdlufy opened this issue Sep 17, 2024 · 6 comments · Fixed by #10079, #10081, #10083, #10108 or #10112
Assignees
Labels
community contribution This issue was closed by a PR from the community contributions welcome Architecture is clear and community can help P2 This issue has medium priority

Comments

@mdlufy
Copy link
Collaborator

mdlufy commented Sep 17, 2024

Description

Migrate other Demo components to the new API page approach as in tuiBlock

Should be visible main properties, appearances and icons
image

@waterplea
Copy link
Collaborator

We would also need to add dropdown controls and textfield controls similarly to appearance as reusable pieces of docs.

@mdlufy
Copy link
Collaborator Author

mdlufy commented Sep 25, 2024

Need to fix #9206

@mdlufy
Copy link
Collaborator Author

mdlufy commented Oct 9, 2024

We need this in InputCard and InputPhoneInternational

@shiv9604
Copy link
Contributor

shiv9604 commented Dec 25, 2024

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.

@waterplea
Copy link
Collaborator

@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!

@shiv9604
Copy link
Contributor

Sure @waterplea. Thanks for your suggestion!

splincode pushed a commit that referenced this issue Jan 10, 2025
@splincode splincode reopened this Jan 10, 2025
splincode added a commit that referenced this issue Jan 17, 2025
@waterplea waterplea reopened this Jan 17, 2025
splincode added a commit that referenced this issue Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment