Phase 22 · Lesson 06

Pagination Filters and URL State

≈ 2 min core reading · 326 source/companion words

Learning contract

What you should be able to do after this

Explain Pagination Filters and URL State without relying on framework buzzwords.
Connect the lesson to the phase outcome: Use TanStack Query as the owner of asynchronous server state with deliberate query keys, freshness, invalidation, mutations, and pagination behavior.
Reproduce the relevant behavior and verify it with evidence.
Diagnose at least one representative failure instead of guessing.

Figure 22.6 — TaskFlow boundary map

component

query key/options

cache

HTTP fetch

server

cache update/invalidation

render

This lesson belongs to Phase 22. Keep the full request/data path visible even when today's code changes only one box.

Instructor workflow: predict first → implement the smallest slice → run it → inspect evidence → break one assumption → diagnose → explain it back. Do not copy the whole code block before understanding the first failing boundary.

Pagination, Filters and URL State Let URL state describe the collection while Query handles remote data

Phase 22 - TanStack Query Volume 06 - Professional Frontend

The URL still owns filters and page number TanStack Query should not replace the Phase 15/20 URL architecture. Search, status, sort and page are navigational state. They belong in search parameters so the view remains refreshable, bookmarkable and shareable.

URL: ?status=DONE&page=3

Next.js searchParams

normalized TaskListQuery

taskKeys.list(query)

TanStack Query cache entry

NestJS collection API

Code

Every page gets a separate cache entry
["tasks", "list", { page: 1, pageSize: 20, status: "DONE" }]
["tasks", "list", { page: 2, pageSize: 20, status: "DONE" }]

Keep previous page visible during navigation import { keepPreviousData, useQuery } from "@tanstack/react-query";

const result = useQuery({ ...taskListOptions(query), placeholderData: keepPreviousData, });

When the key changes from page 1 to page 2, the second page is a distinct query. keepPreviousData lets the previous successful result remain visible while the new page is fetched and exposes isPlaceholderData so Next can be disabled until the next page is known.

Reset page when filter identity changes

If a user is on page 8 and changes status or search, navigation should normally set page back to 1. That remains URL logic, not cache logic.

Do not make the key enormous by accident

Use a normalized query object containing only values that affect the API response. Do not insert router objects, functions, class instances or access tokens into a query key.

Prefetch the likely next page - only when justified Once pagination is stable, TaskFlow can prefetch page N+1 when metadata says a next page exists. This can make navigation feel instant. It is an optimization, not a correctness requirement, and should not multiply requests for pages the user is unlikely to visit.

if (result.data.meta.hasNextPage) { queryClient.prefetchQuery( taskListOptions({ ...query, page: query.page + 1 }), ); }

Because the next page has its own query key, prefetching warms exactly that cache entry without replacing the currently displayed page.

Executable lesson studio · state

Now turn the explanation into engineering skill.

Pagination Filters and URL State matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.

By the end, you should be able to

Explain Pagination Filters and URL State in terms of concrete inputs, ownership, outputs, and evidence.
Implement or reproduce the smallest TaskFlow slice that demonstrates this state concept.
Diagnose one representative state failure using observable evidence instead of trial-and-error.

Figure 22.6B — Mental model

value

owner

lifetime

source of truth

consumer

Read left-to-right while implementing. When debugging, walk right-to-left until the first observed fact differs from your prediction.

Code-along sequence

One coherent change at a time

01
Restate the goal of “Pagination Filters and URL State” as one observable behavior. Write the success signal before touching code.
02
Trace the boundary map: value → owner → lifetime → source of truth → consumer. Mark the one boundary this lesson changes.
03
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
04
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
05
Connect the slice to TaskFlow’s phase artifact: TaskFlow query/mutation layer with stable keys, list/detail caching, invalidation, filters, and debugging via devtools/logs.. Verify behavior from the outside as a user or API client would.
06
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
07
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.

txtClassify before choosing a state tool

API task rows       -> TanStack Query
Search/filter URL    -> URL/search params
Create form fields   -> React Hook Form
Dialog open/closed   -> local UI state
Authenticated user  -> auth/session state

Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.

Verification

Prove the happy path

Run the narrowest relevant command or request and require a clean exit/status.
Inspect the boundary-specific evidence: terminal output, Network panel, database row/query plan, test report, container health, or deployment logs.
Repeat the behavior once after the change so a one-off cached or stale result cannot masquerade as success.

Break it on purpose

Build debugging memory

Copying query data into useState/useEffect
Change one assumption in the state example—identity, input, configuration, ordering, connectivity, or state—and predict the exact symptom before running it.

SymptomInvestigation path

Expected result does not appear

Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.

A shortcut appears to fix it

Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.

Closed-reference challenge

Can you transfer the idea?

Without copying the final source, create a second small scenario that applies “Pagination Filters and URL State” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.

Explain-back

Answer these without reopening the solution

What problem does Pagination Filters and URL State solve in TaskFlow, and what would be observably wrong without it?
Which part of the state boundary owns the decision, and which neighboring layer must not own it?
What evidence proves the happy path instead of merely suggesting it worked?
Name one realistic failure or abuse case and the first place you would inspect.
If requirements doubled tomorrow, which part of this design should stay stable and which part is allowed to change?

Lesson studio

Turn the reading into skill

Do it

Add pagination/filter URL state and inspect how query keys prevent cross-filter cache corruption.

Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.

Break it safely

Copying query data into useState/useEffect

Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.

Explain it back

Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?

If your explanation is vague, repeat the boundary trace before moving on.

Exit ticket

Before marking complete

Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.

← Authenticated Task Queries End to End Mutations and Targeted Invalidation →