Gracefully handle version restore
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: conflict resolution
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
When restoring a version through the web UI we should make sure to handle this without a conflict.
Similar how https://github.com/nextcloud/richdocuments/pull/3152 does this, we can use the events to detect the restore from https://github.com/nextcloud/server/pull/40184
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
Review the web UI version-restore flow and the event-based approach in richdocuments pull request 3152, then compare it with the server events from pull request 40184. Done means restoring a version through the UI no longer causes a conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100