Query

Server Input

Pass resolved query input to server procedures instead of rebuilding filter state in table code.

Query owns the shape of server input for filters, sorting, and pagination.

Client screens should pass resolved query controller input to API calls instead of manually rebuilding search params or table state.

Pattern

const input = useDeferredValue({
  pagination: pagination.input,
  filters: filtering.input,
  sorts: sorting.input,
});

Pass that input into ORPC query options or another server API boundary.

Pagination

Use query pagination strategies for URL-backed page and limit state.

URL State

Keep filters, sorting, and pagination shareable through URL-backed query state.