When implementing pagination in React, which state variables are commonly tracked?

When implementing pagination in React, which state variables are commonly tracked?

• A. startIndex and perPage
• B. totalCount and pageIndex
• C. offset and limit
• D. page and limit

Answer: (D)

The key ideas in pagination state are the current page and how many items to show per page. The current page tells you where you are in the data, and the limit defines the page size. With those two, you can compute exactly which slice of data to display or fetch: start = (page - 1) * limit, and you show limit items. This setup matches how users interact with pagination—a page number control and a page-size control—and it aligns with many APIs that accept page and limit parameters. It also makes it easy to calculate total pages when you know the total item count: totalPages = Math.ceil(totalCount / limit). While other naming schemes like offset with limit or startIndex with perPage exist, page and limit are the most intuitive for React state because they map directly to user actions and to common API patterns.

The key ideas in pagination state are the current page and how many items to show per page. The current page tells you where you are in the data, and the limit defines the page size. With those two, you can compute exactly which slice of data to display or fetch: start = (page - 1) * limit, and you show limit items. This setup matches how users interact with pagination—a page number control and a page-size control—and it aligns with many APIs that accept page and limit parameters. It also makes it easy to calculate total pages when you know the total item count: totalPages = Math.ceil(totalCount / limit). While other naming schemes like offset with limit or startIndex with perPage exist, page and limit are the most intuitive for React state because they map directly to user actions and to common API patterns.