mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-16 06:08:33 -05:00
[GH-ISSUE #2563] Create Share Link - Only the first 20 resources are available #12995
Reference in New Issue
Block a user
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 @aweb-01 on GitHub (Feb 28, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2563
Originally assigned to: @miloschwartz on GitHub.
Describe the Bug
When I go to create a Share Link, in the "Resource"/"Select Resource" dropdown, only the first 20 resources (as shown on my "Network --> resources --> public" page are available. None of the resources on the 2nd page are available, and if I search for them I get "No resources found".
Environment
To Reproduce
When I go to create a Share Link, in the "Resource"/"Select Resource" dropdown, only the first 20 resources (as shown on my "Network --> resources --> public" page are available. None of the resources on the 2nd page are available, and if I search for them I get "No resources found".
Expected Behavior
all resources appear when searched
@LaurenceJJones commented on GitHub (Feb 28, 2026):
Issue happens because sharelink form only sends a default request to organization resources, the default pageSize is 20 if query parameter is not provided
72bf6f3c41/server/routers/resource/listResources.ts (L42-L53)Since the dropdown is limited in functionality we should consider:
pageSize=0to get all resources?investigated will work but causes a scalable issue
/api/v1/org/{org}/resources/searchto search all entries instead of client side filteringinvestigated original endpoint already has a query parameter we just need to send this from the search box inside the dropdown.
needs more investigation
@oschwartz10612 commented on GitHub (Feb 28, 2026):
Ahh yep this is a mistake due to the new pagination in 1.16. Will fix and do a new patch.
@oschwartz10612 commented on GitHub (Feb 28, 2026):
Fixed in 1.16.2 though we will need to fix it properly in the future.