Cloning a deck wouldn't clone the attachments...
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Hello there,
The issue is quite straightforward, so I believe no additional explanation is necessary.
When a deck is cloned, the attachments of the cards are not copied along with it, and they currently have to be uploaded manually.
Nextcloud version: Nextcloud Hub 10 (31.0.10)
Deck version: 1.15.5
We would greatly appreciate it if this functionality could be added in a future update. Thank you! :)
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
The issue names no files, tests, or entry points. Start by locating the deck-cloning implementation and the code that handles card attachments, then trace how a cloned card is created. Done means cloning a deck also copies its card attachments without requiring manual uploads, with regression coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100