alreadyExists error for create
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.4k
- Forks
- 100
- Avg merge
- 18h 7m
- Merged PRs (30d)
- 2
Description
The alreadyExists SetError is defined in Core for /copy. For Mail at least, this might be something the server wishes to return on create in /set too if it forbids identical content (if it just forbids identical message-id, it probably makes more sense to return invalidProperties). It's unclear if this is a curiosity of mail or might be more generally applicable. If we ever do a rev2 of the spec, we should have enough implementation experience (across multiple domains, not just email) to determine and fully define this.
Contributor guide
No contributing guide indexed for this repository
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 with the Core alreadyExists SetError definition and compare its /copy semantics with Mail creation in /set. Check whether identical content versus identical message-id is the relevant distinction, and whether the behavior applies beyond Mail. Done means reaching a cross-domain decision and fully defining the change for a future specification revision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100