Conflict resolution view
Open
enhancement
stale
- Dominant language
- TypeScript
- Stars
- 189
- Forks
- 37
- Avg merge
- 17h 18m
- Merged PRs (30d)
- 17
Description
When #203 will be implemented, the server will return a 412 response if someone else changed the object in the mean time.
In some previous versions of the Kinto admin, we had a conflict resolution view that we could reuse in this case :)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading issue #203 to understand the 412 response, then locate the conflict resolution view from previous Kinto admin versions for possible reuse. Done means the admin presents that view when another user has changed the object and the server returns 412.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100