Skip to content

[bug]: No restriction on perPage param #1019

@duytanisme

Description

@duytanisme

Describe the bug

When testing with perPage=1000 in the URL params, it still worked — meaning there’s currently no limit on page size. I tried adding 50,000 mock records locally, and loading all of them took a long time. We should enforce a maximum page size to prevent users from requesting excessively large datasets and overloading the frontend.

How to reproduce

  1. Go to any paginated endpoint or page in the app.
  2. Open the browser’s address bar.
  3. Manually change the perPage query parameter to a large number (e.g., perPage=1000 or perPage=50000).
  4. Press Enter to reload the page.
Image

Link to reproduction

https://tablecn.com

Additional information

I'm not sure if this behavior is expected.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions