Set maximum records limit per-page in config. - #3171
Open
gemul wants to merge 1 commit into
Open
Conversation
|
Owner
|
Thanks for the PR! The changes look good, however, I suspect this might break the export functionality of buttons package. Will check further when I get the chance. |
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
2 participants
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.
This PR adds a
max_limitconfiguration to prevent end-users from arbitrarily setting a large value for thelengthrequest parameter, which could otherwise cause the server to overload if not handled manually (e.g., in middleware).If the
lengthvalue exceeds this limit, it will be overridden with the specifiedmax_limit.The default value is 100.