Page size hardcoded in frontend datasource
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Description
The PageableListDatasource uses a hardcoded page size (20 items) with no way to configure it per use case.
Location
Appy/Appy-frontend/src/app/shared/services/datasource.ts
Risk
All paginated lists use the same page size regardless of the screen size or data density. Users with large datasets or small screens have no recourse.
Suggested Fix
Make page size a configurable parameter on PageableListDatasource, with the current hardcoded value as the default, so individual pages can override it as needed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Appy/Appy-frontend/src/app/shared/services/datasource.ts and read PageableListDatasource plus its consumers. Confirm how the current 20-item value is applied and check whether existing usage depends on it. Done means callers can provide a page size while existing callers retain the default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100