Pagination

Collections that do not fit in one response

An API that returns thousands of rows sends them a page at a time:

{"page": 1, "total_pages": 3, "has_next": true, "users": [...]}

Fetching them all means looping until the server says stop. Two rules keep it safe:

1. Trust the server's signal, not your own arithmetic. has_next or comparing against total_pages beats guessing when an empty page means the end.
2. Have a ceiling. A bug in the API — or in your loop — should not fetch a million pages. A max_pages limit turns a runaway into a bounded mistake.

The fake /users endpoint returns two users per page across three pages.

Your turn: write fetch_all_users(max_pages=10) returning every user, following the pages until has_next is false.