Repository navigation
Cursor pagination has no unique tie-breaker #280
Description
Summary
/streams orders by createdAt only and /ngos orders by name or
createdAt only, while both paginate with an id cursor. Streams created in
the same ledger share a createdAt (it is set from ledgerClosedAt), so
page boundaries can skip or repeat rows. Only the activity and
recent-streams queries add id.
Acceptance criteria
- Add
idas a secondary sort key to every cursor-paginated query. - Add a test with rows that share a timestamp spanning a page boundary.
Getting started
Fork this repository, clone your fork, and add this repo as upstream:
git clone https://github.com/<your-username>/streamgive-backend.git
cd streamgive-backend
git remote add upstream https://github.com/StreamGive/streamgive-backend.gitCreate a branch for this issue:
git checkout -b fix/pagination-tiebreakerSuggested commit message:
fix: add a unique tie-breaker to cursor pagination
Run npm run lint, npm run typecheck, and npm test before pushing, then
open a pull request from your fork against main and link this issue. See
the contributing guide for the full contribution guide.
Activity
Michvista commentedon Oct 18, 2026
@Michvista has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Michvista to this issue.
charliechinedu19-netizen commentedon Oct 18, 2026
@charliechinedu19-netizen has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @charliechinedu19-netizen to this issue.
AMDYFX commentedon Oct 18, 2026
@AMDYFX has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @AMDYFX to this issue.
drips-wave commentedon Oct 18, 2026
Congratulations, @AMDYFX! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @AMDYFX: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
github-actions commentedon Oct 18, 2026
Closed by #340, which was merged automatically.
drips-wave commentedon Oct 18, 2026
This issue has been completed by @AMDYFX as part of the Stellar Wave Program's 10th Wave 🥳
😎 @AMDYFX: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.