Query
URL State
Keep filters, sorting, and pagination shareable through URL-backed query state.
Many Tulip data surfaces use URL-backed query state so users can share, reload, and navigate table views predictably.
Query controllers own that state and expose resolved input to the rest of the screen.
What belongs in URL state
- active filters
- sorting choices
- pagination position
- search terms when they define the result set
What should stay local
- open menus
- selected rows unless deep linking needs it
- transient input draft state
- modal state