indexed-store pagination
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 747
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
In the source code I do not see a way that LogPage.next could exist. Does this implementation load all entries into memory (not paginating them)?
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 at indexed-store/index.js line 89 and trace how LogPage.next is created or consumed. Check whether the indexed-store implementation loads all entries into memory rather than paginating them. Done means establishing whether LogPage.next can exist in the current implementation and documenting or addressing the discrepancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100