loved the work you've done with this! excited about server-side filtering support!
Thanks Tahir. If you're interested in trying it out, join our Discord server: https://ui.bazza.dev/chat
Tracking "The Great Decoupling" in a separate request! https://feedback.ui.bazza.dev/board/p/the-great-decoupling
Work has begun on this, starting with "The Great Decoupling" from TanStack Table. We still love and support TST, but we want to make it easier for folks who aren't using it to still get amazing filters for their data tables. <3
Love the filter component! When you decouple it and make it possible to do server side filtering, it would be great to be able to choose which columns and which filters are enabled. Some filters can be very expensive for the DB. Keep up the good work!
You'll have full control over which columns are filtered, since you'll need to pass in some info about each column (i.e. data type being stored, label, icon, etc.) :)
Also you can take a look at https://github.com/ljharb/qs for a standard on params (can be used server and client side)
Noted, thanks for this!
Also, with Nuqs support (already in alpha it seems?), you're halfway through server-side support as the URL is available in both the client and server. You just need to handle loading state on filters and handle logic for applying the filter. (User needs to be aware which filters are already applied and which are in the process of being applied as server filtering is not instant like client filtering. Though another approach would be to let the user to indicate loading state outside the table/filters with something like a spinner/loader, nprogress, etc)
Huge upvote. Decoupling components is a good idea regardless of whether client or server-side
Available now: https://ui.bazza.dev/changelog/2025-05-05-v0.2