mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #5931] [bug]: Team collections sidebar only renders 10 root-level collections #2330
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2330
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @alschenk on GitHub (Mar 3, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5931
Is there an existing issue for this?
Platform
Web App
Browser
Edge
Operating System
Windows
Bug Description
Is there an existing issue for this?
I have searched the existing issues and couldnt found the exact problem. But these seem to be related cause: #2096, #5426
Current behavior
When a team has more than 10 root-level collections, only 10 are rendered
in the sidebar. The 11th and beyond are silently invisible — no scroll,
no pagination indicator, no error.
The collections exist correctly in the database with valid orderIndex values
and no missing parentID. Deleting any visible collection causes the previously
hidden one to appear, confirming it is a rendering/pagination cutoff at exactly 10.
Expected behavior
All root-level team collections are rendered regardless of count.
Steps to reproduce
Environment
Suspected cause
Seems like same root cause as #5426 — the GraphQL/REST list query uses a default
page size of take=10 with no follow-up cursor request, so items beyond
the first page are never fetched.
Deployment Type
Self-hosted (on-prem deployment)
Version
v2026.2.0
@jamesgeorge007 commented on GitHub (Mar 3, 2026):
Thanks for the detailed report. Closing in favour of #5908. Please follow it for updates.