Skip to content

Conversation

@pjehan
Copy link

@pjehan pjehan commented Sep 13, 2025

According to the configuration docs, pagination_client_enabled defaults to false. This means clients cannot use ?pagination=false to disable pagination, even though pagination itself is enabled by default.
Setting pagination_client_enabled=true allows clients to control pagination via the query parameter. I confirmed this behavior - when set to true, the pagination query option becomes available and clients can then disable pagination for specific requests.

The key distinction is:

  • pagination_client_enabled=false: Pagination is always on, no client control
  • pagination_client_enabled=true: Clients can choose to disable pagination with ?pagination=false

The pagination_client_enabled should be true instead of false to enable client side pagination.
@vinceAmstoutz
Copy link
Member

vinceAmstoutz commented Sep 17, 2025

@pjehan As you can see here, the goal is to disable client-side pagination globally. That's why you'll find pagination_client_enabled: false (which disables it).

@pjehan
Copy link
Author

pjehan commented Sep 18, 2025

@vinceAmstoutz The documentation on this point is confusing.

According to the configuration docs, pagination_client_enabled defaults to false. This means clients cannot use ?pagination=false to disable pagination, even though pagination itself is enabled by default.
Setting pagination_client_enabled=true allows clients to control pagination via the query parameter. I confirmed this behavior - when set to true, the pagination query option becomes available and clients can then disable pagination for specific requests.

The key distinction is:

  • pagination_client_enabled=false: Pagination is always on, no client control
  • pagination_client_enabled=true: Clients can choose to disable pagination with ?pagination=false

I just tried it and if the parameter is set to true, the pagination query option appear and then I can choose to actually disable the pagination for this endpoint:
image

@vinceAmstoutz
Copy link
Member

vinceAmstoutz commented Sep 18, 2025

@vinceAmstoutz The documentation on this point is confusing.

According to the configuration docs, pagination_client_enabled defaults to false. This means clients cannot use ?pagination=false to disable pagination, even though pagination itself is enabled by default.
Setting pagination_client_enabled=true allows clients to control pagination via the query parameter. I confirmed this behavior - when set to true, the pagination query option becomes available and clients can then disable pagination for specific requests.

The key distinction is:

  • pagination_client_enabled=false: Pagination is always on, no client control
  • pagination_client_enabled=true: Clients can choose to disable pagination with ?pagination=false

I just tried it and if the parameter is set to true, the pagination query option appear and then I can choose to actually disable the pagination for this endpoint:
image

@pjehan Thanks for the additional information 🙂 I'm going to create a documentation PR to avoid any confusion on it and improve the DX(developer experience). Could you please update the PR description before? 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants