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.

Sign up for GitHub

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

Jump to bottom

Get rid / unify poke front specific components #7747

Open
JulesBelveze opened this issue Sep 30, 2024 · 2 comments
Open

Get rid / unify poke front specific components #7747

JulesBelveze opened this issue Sep 30, 2024 · 2 comments
Assignees
@JulesBelveze

Comments

@JulesBelveze
Copy link
Contributor

JulesBelveze commented Sep 30, 2024 •
edited
Loading

We currently have poke specific components, which are similar to sparkle ones. This require to maintain both, which doesn't make much sense.

Like PokeDataTable and stuff
@JulesBelveze JulesBelveze self-assigned this Sep 30, 2024
@JulesBelveze JulesBelveze mentioned this issue Sep 30, 2024
Merged
@spolu
Copy link
Contributor

spolu commented Oct 28, 2024

sitrep?

@JulesBelveze
Copy link
Contributor Author

Not there yet, there's still a bunch of stuff to implement in in sparkle to be able to fully get rid of front/components/poke/shadcn/.

Most of the work is on Table and DataTable as well as forms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JulesBelveze JulesBelveze

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@spolu @JulesBelveze