Creating shares for attached files will litter the top-level view of all new users
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Describe the bug
When a user attaches a file in a card, the file will be uploaded into a local decks folder in the user's storage, and the file will then be shared with all other users. This will result in a very "dirty" and confusing top level folder for most new users within your Nextcloud instance. It makes for a bad onboarding experience, if there's dozens of files, whose origin is unknown to the user.
Expected behavior
There should be a different way to add files to a Card (not selecting existing files), without creating a standalone share for every file.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the card attachment flow described in the issue and trace how the upload reaches the user's local decks folder and becomes a share. Done means adding files to a Card no longer creates confusing standalone shares in new users' top-level views, but the issue does not name an entry point, file, or test to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100