Fix shared collections appearing in owned tab by using correct API endpoint #876
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The collections page was incorrectly displaying shared collections in the "owned" tab because the frontend was calling the wrong API endpoint.
Problem
The frontend was fetching owned collections from
/api/collections/which returns both owned AND shared collections, causing shared collections to appear in the owned tab where they shouldn't be.Backend API Analysis
/api/collections/(list method):Q(user=request.user.id) | Q(shared_with=request.user)- returns both owned and shared collections/api/collections/all/(all method):Q(user=request.user)- returns only owned collections/api/collections/shared/(shared method):shared_with=request.user- returns only shared collectionsSolution
Changed the frontend to use the correct endpoint for owned collections in
/frontend/src/routes/collections/+page.server.ts:Impact
This ensures proper separation of collections across the three tabs: owned collections only appear in the "owned" tab, shared collections only appear in the "shared" tab, and archived collections only appear in the "archived" tab.
Fixes #875.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
127.0.0.11flagcdn.compython manage.py download-countries(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.