Optimize api for large datasets
Open
enhancement
- Dominant language
- Shell
- Stars
- 2
- Forks
- 5
- PR merge metrics
- PR metrics pending
Description
**Feature request**
It would be great to have pagination for core.
**Use case**
Many users need this functionality for production deployments.
**Implementation idea**
Add a new config option `enable_pagination` with default `false`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the core API entry point and configuration handling for `enable_pagination`; the issue does not identify specific files, resources, or response shapes. Define which large-dataset responses are in scope, how pagination should behave, and verify that the default-disabled setting is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100