POST should be PUT
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 121
- Avg merge
- 5h 52m
- Merged PRs (30d)
- 1
Description
Technically, POST should be idempotent, so as implemented PUT would be more appropriate for routes like /api/collections.
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 by locating the route definitions for /api/collections and checking how the current POST handling is exercised. Update the route and its coverage so the collection operation uses PUT, then verify that repeated equivalent requests are idempotent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100