API addition without API version bump (attachment deletion)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 738
- Forks
- 162
- Avg merge
- 6h 2m
- Merged PRs (30d)
- 35
Description
Hello, great work getting #1623 resolved, many thanks 🙏
I'm looking forward to getting it integrated into API consumer Iotas and will make changes to make use of the attachment deletion ability. I noticed however that there's no clean way to determine whether attachment deletion exists on the server, beyond say comparing the app version or detecting the specific failure.
Bumping the API version would be ideal.
Server
- Notes app version: 6.1.0
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
No files or tests are named. Start by reviewing the attachment-deletion API work in #1623 and locate the project's API version declaration; confirm how consumers can detect support for attachment deletion. Done means the API version clearly reflects that addition and the relevant version behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100