-
Notifications
You must be signed in to change notification settings - Fork 607
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
[Table] Implement component #2139
Comments
It is recommended to provide I believe that refs: [Shadcn] |
This logic works for shadcn because they provide a primitive for each HTML element of the table. However, in Nuxt UI you will still have to pass a |
I will explain my reasons for your reference: First of all, I hope to have a fully controllable table content rendering method while maintaining a unified UI style. Secondly, with the increase of functional requirements, Datatable will have a lot of internal complexity, which sometimes only It is too heavy to render an ordinary table. After clarifying, I want to say that developing a separate table component will not increase much workload, because its style can be completely inherited by Datatable, and because the table component contains almost no functions, there is almost no need for maintenance in the later stage. If you think table is completely unnecessary, or for compatibility with v2, I completely understand what you are saying, just clarifying my idea 🤔 |
Feature request for table. I think it would be great to also have error state just like loading or empty state. |
No description provided.
The text was updated successfully, but these errors were encountered: