Validation, Errors, Filtering and Pagination

MODULE 14 · LESSON 14.2

Return stable machine-readable failures and bounded list responses.

Practice-firstBeginner-friendlyProduction-aware

From mental model to working change

Good work on Validation, Errors, Filtering and Pagination leaves evidence: a visible behavior, a stable contract or a repeatable operational check. This lesson defines an application trust boundary, where an explicit contract is safer than framework convention or an undocumented assumption.

Here, that decision supports a specific checkpoint: Turn CourseFlow endpoints into a documented, versionable API. A reviewable result should include a repeatable request, automated test, query result and failure response rather than a claim that the feature simply works.

Validation, Errors, Filtering and Pagination workflowA four-step visual showing problem details, cursor pagination, filtering, rate limits.Validation, Errors, Filtering and Pagination workflow1Problem Details2Cursor Pagination3Filtering4Rate Limits

Validation, Errors, Filtering and Pagination workflow

  1. 1Problem Details
  2. 2Cursor Pagination
  3. 3Filtering
  4. 4Rate Limits
Validation, Errors, Filtering and Pagination workflow: a practical sequence used in this lesson.

A practical model for validation, errors, filtering and pagination

Return stable machine-readable failures and bounded list responses. The useful unit of understanding is the boundary: who owns the decision, which input crosses it, what result is visible and how a failure is reported.

  • Problem Details: Connect this concept to the module checkpoint and identify the evidence a reviewer should expect.
  • Cursor Pagination: Explain the concept without framework jargon, then point to it in the working example.
  • Filtering: Decide what belongs in code, configuration, data or documentation and explain why.
  • Rate Limits: Name its input, observable result and most likely failure in this lesson.

Follow the data through the example

The sample is intentionally narrow. Its job is to expose problem details without hiding the decision behind unrelated setup.

JSON
{
  "type": "https://example.com/problems/validation",
  "title": "Validation failed",
  "status": 422,
  "errors": [{"field":"email","code":"invalid"}]
}
Review it as someone else's change

Explain what the sample proves, what it does not prove, and which test would increase your confidence in cursor pagination.

Ship a reviewable increment

  1. 1
    Problem Details

    Describe the behavior in one sentence, then choose the smallest input that can prove it.

  2. 2
    Cursor Pagination

    Add this responsibility at the narrowest sensible boundary; do not pull an unrelated layer into the change.

  3. 3
    Filtering

    Run the focused example and save the output, trace, query or screenshot that confirms the result.

  4. 4
    Rate Limits

    Break one assumption on purpose, make recovery clear and record the trade-off you accepted.

Risks to catch during review

  • Treating problem details as vocabulary instead of defining the behavior it must produce.
  • Testing the expected path while ignoring an empty, invalid, repeated or unauthorized case around cursor pagination.
  • Allowing filtering to cross a boundary without an explicit contract or useful error.
  • Changing several layers before capturing the first piece of evidence, which makes the original cause harder to see.

A repeatable investigation sequence

  1. Reduce the problem to the smallest failing Validation, Errors, Filtering and Pagination case.
  2. Capture the actual input and output at the problem details boundary.
  3. Read the first relevant error, request, trace or query rather than the loudest downstream symptom.
  4. Test one explanation for the failure in cursor pagination; avoid changing two variables together.
  5. Keep a regression check that would expose the same defect if it returned.

Security decision

Validate external input, authorize the requested action, use parameterized data access, and keep credentials out of responses, source control and logs.

Performance decision

Bound queries and collections, inspect the actual request or query plan, and optimize only the slow boundary confirmed by evidence.

PRACTICE

Build something you can inspect

Add cursor pagination and a documented validation-error shape to the course list.

Stretch challenge

Ask another person to run the exercise from your README. Fix the first place where their result differs from yours.

Definition of done

  • The behavior around problem details works with realistic input.
  • A failure involving cursor pagination is handled clearly and without leaking sensitive detail.
  • The implementation remains keyboard-usable when it produces an interface.
  • Your evidence directly supports the claim made in the exercise.
  • The README records the important trade-off without pretending the solution is universal.

Check your reasoning

Why can unbounded collection endpoints become a reliability and cost risk?

Answer by naming the expected problem details behavior, the layer responsible for it and the evidence that would confirm your explanation.

Where would you investigate the first failure?

Start where cursor pagination crosses a boundary. Compare the actual input and output there before following downstream symptoms.

What would make this work reviewable?

Show the focused change, repeatable steps, the result of your check and one honest trade-off connected to filtering.

What to carry into the next lesson

  • Return stable machine-readable failures and bounded list responses.
  • Keep problem details visible at the boundary where it can be tested.
  • Use evidence from cursor pagination before widening the implementation.

References and related reading

Progress is stored only in this browser.

Share this page

Share this page with the people who will use it next.

X Facebook LinkedIn WhatsApp Email

Discussion

No comments yet. Add the first useful question or observation.