Add resource-level override for 'OPTIMIZE_PAGINATION_FOR_SPEED'#1569
Merged
nicolaiarocci merged 7 commits intopyeve:masterfrom Mar 19, 2026
Merged
Add resource-level override for 'OPTIMIZE_PAGINATION_FOR_SPEED'#1569nicolaiarocci merged 7 commits intopyeve:masterfrom
nicolaiarocci merged 7 commits intopyeve:masterfrom
Conversation
Member
|
A solid upgrade, thank you. Would you mind upgrading the documentation as well? |
Contributor
Author
|
Thank you! Absolutely, I'll push the documentation in this PR. |
Contributor
Author
|
I've documented the option in the "Resource / Item Endpoints" section. I had to adjust the indentation for all descriptions to accommodate the longer option name and keep everything aligned. |
nicolaiarocci
added a commit
that referenced
this pull request
Mar 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OPTIMIZE_PAGINATION_FOR_SPEEDis currently a global-only setting. This is problematic for APIs with mixed requirements: high-volume resources need the speed optimization (no total count), while smaller resources could require an accurate total for the UI/frontend.This PR introduces a resource-level setting
optimize_pagination_for_speedthat allows granular control, overriding the global configuration when defined.