floccusaddon / floccusaddon/floccus
Linkwarden sync failed when trying to update an read only collection
- Dominant language
- JavaScript
- Stars
- 8.5k
- Forks
- 327
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 2
Description
### Describe the feature you'd like to request
This is more of an usability enhancement then a bug I guess, but I was testing the Linkwarden sync with multiple users today and if a user only has read only (viewer) access to a collection the sync works great, but if you try to create or edit links in the browser the sync will obviously fail.
Manually using the "pull down" profile button will reset the synced folder in the browser and the sync is working again.
### Describe the solution you'd like
Maybe it's possible to at least show a better error message when trying to edit a read only collection as I think it's not easily possible to actually prevent the user from making changes to the bookmark folder in the browser or is there a better way?
I checked the Linkwarden API and when creating a link without permission the response is "Collection is not accessible.". Maybe you can make use of the collection member info from the API, e.g. "canCreate": false, "canUpdate": false, "canDelete": false before trying to update the collection.
### Describe alternatives you've considered
I think it may not always be clear to the actual user why the sync failed as you can even create a Linkwarden collection with full access and a sub-collection has read only access only.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the Linkwarden sync flow used by the browser's pull-down profile action and inspect how the API response "Collection is not accessible." is handled. Check the collection member permissions mentioned in the issue, then verify that attempts to edit read-only collections produce a clear error and that pulling the profile restores synchronization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100