Drafts: save attachments too
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature parity
feature:drafts
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
This is not too important as it’s a lot to save and not really a pain point at the moment.
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 and only suggests saving attachments with drafts. Start by clarifying the expected draft and attachment behavior and locating the relevant draft-handling flow. Done should mean the agreed attachment-saving behavior is implemented and verified, but the current issue does not define those criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100