Pagination and Search

Paginate the feed and search post text.

Goal

This snapshot advances Tidepool Notes by teaching you to paginate the feed and search post text.

Every numbered folder is a complete app. Run this stage independently, then compare it with the previous folder.

Prerequisites

Use Node.js 20+, npm, and a terminal. You should recognize React components, TypeScript modules, and HTTP verbs.

Port 3004 must be free. Copy .env.example before starting database stages.

  • Node.js and npm
  • A code editor and terminal
  • Docker from part 4 onward

Concepts

Pagination bounds work per page. Search filters with case-insensitive title matching before counting and slicing.

Keep the server boundary visible: Remix loaders read trusted data on the server; actions must validate input and re-check authorization before mutations.

Walkthrough

Use page size 5, compute total pages, and accept a q query parameter.

Read the example, then open the matching snapshot. The repository includes the surrounding setup and error handling.

const pageSize = 5
const pages = Math.max(1, Math.ceil(total / pageSize))

Run and verify

Enter 10-Pagination-And-Search, install dependencies, copy .env.example when present, and start Remix on port 3004.

Open http://127.0.0.1:3004. Watch the terminal for validation and database errors.

docker compose -f ../docker-compose.yml up -d
git clone https://github.com/michaeldunga1/fcc-remix-blog.git
cd fcc-remix-blog/10-Pagination-And-Search
npm install
cp .env.example .env
npm run db:push
npm run db:seed
npm run dev

Troubleshooting

Off-by-one errors often come from mixing 0-based offsets with 1-based page numbers.

Missing-module errors usually mean npm install ran in another snapshot. For Postgres failures, confirm Docker and the tidepool_NN database name.

  • Read the first error first
  • Restart after environment changes
  • Never commit .env or node_modules

Try this

Search for ownership and confirm matching cards.

Test a happy path and one invalid or unauthorized request.

  • Make one small change
  • Test it in the browser
  • Compare with the next snapshot only after it works