Putting the same resource that already exists should not result in a change
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 15
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
OADA should compute the difference between the put body and the existing result. Empty diffs should translate into a no-op, not update rev, nor create a change. This would make writing data sync microservices much easier / correct.
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 PUT request handling and the logic that compares stored resources, updates rev, and creates changes. Trace how an identical put body is processed; done means an empty difference leaves the resource, revision, and change history unchanged, with tests covering that no-op behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100