This repository was archived by the owner on Jan 29, 2026. It is now read-only.
[WIP] Add default pagination limits for list endpoints#92
Draft
[WIP] Add default pagination limits for list endpoints#92
Conversation
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.
Original prompt
This section details on the original issue you should resolve
<issue_title>[API] Implement Default Pagination Limits for List Endpoints</issue_title>
<issue_description>## 📊 Priority: LOW - Nice to Have
Background
The workflow and store list endpoints support pagination via
limitandoffsetquery parameters, but do not enforce default limits when these parameters are omitted. This could lead to performance issues if the database grows large, as clients might unintentionally request thousands of records.Current Implementation - No Default Limits
Problems Without Default Limits
Real-World Scenario
Recommended Solution
Part 1: Define Pagination Constants
Part 2: Update WorkflowService
Part 3: Update StoreService
Part 4: Update API Response Format