---
title: "Discussion on \"Your pagination buttons should read the API's meta, not your own props\" | Hashnode"
description: "Discussion on \"Your pagination buttons should read the API's meta, not your own props\". I have seen pagination components that take totalPages as a prop and compute it themselves from a count. Then the backend changes the page size from 15 to 25, and the frontend cheerfully shows the wro"
url: "https://hashnode.com/posts/your-pagination-buttons-should-read-the-api-s-meta-not-your-own-props/6adaee020a82624ab9871741"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Your pagination buttons should read the API's meta, not your own props](https://kamrankhandev.hashnode.dev/your-pagination-buttons-should-read-the-api-s-meta-not-your-own-props?utm_source=hashnode&utm_medium=feed)

I have seen pagination components that take totalPages as a prop and compute it themselves from a count. Then the backend changes the page size from 15 to 25, and the frontend cheerfully shows the wro

Oct 23 · 2 min read · kamrankhandev.hashnode.dev  
Read the article

-   [#react](https://hashnode.com/tag/react)
-   [#laravel](https://hashnode.com/tag/laravel)
-   [#javascript](https://hashnode.com/tag/javascript)
-   [#webdev](https://hashnode.com/tag/webdev)
-   [#saas](https://hashnode.com/tag/saas)

## Written by

[Kamran Khan](https://hashnode.com/@kamrankhandev)

@kamrankhandev · Lahore, Pakistan

  
[View profile](https://hashnode.com/@kamrankhandev)

Full-Stack Web Developer (React.js + Laravel) | Dashboards, SaaS Apps & Management Systems for Global Clients

Full-Stack Web Developer working with React.js and Laravel. I build dashboards, SaaS applications, and business management systems for clients worldwide. I write about real patterns from client work — API design, React architecture, and indie hacking.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
