Two Tables, One URL: Solving Inertia.js State Collisions If you've worked with Inertia.js...
Two Tables, One URL: Solving Inertia.js State Collisions
If you've worked with Inertia.js + TanStack Table for server-side filtering and pagination, you know how satisfying the pattern feels.
A single router.get() call gives you a lot for free:
Filter state lives in the URL
Links are shareable
You're storing filter state, search queries, and pagination in useState — and losing it every time someone refreshes. The URL…
Every dashboard eventually needs the same three things. A search box, a few filters, and pagination...
How many times have you installed a massive routing framework just to parse a query parameter or...
Every data table, search page, and filtered list has the same problem: the user applies a filter, the...
My Dessert Shop Dashboard Was Choking on Its Own Data — Here's the Architecture That Fixed...
Nowadays, web frameworks come with ✨ magic ✨. Some more than others, but all of them have some. The...
