Enable multi user working
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
If user A loads the map, changes something, User B loads the map, changes something, User A saves and then User B saves, the changes of User A will be overwritten.
Apply Optimistic Offline Lock / https://martinfowler.com/eaaCatalog/optimisticOfflineLock.html to solve the issue.
In case a conflict arises, the save should be blocked - and the map updates "merged" in the current map. That can also be as a diff from loaded-state to server-state as console output.
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
No files, tests, or entry points are named. Start by tracing how maps are loaded and saved, then read the linked Optimistic Offline Lock references. Done means concurrent saves are detected, the later save is blocked on conflict, and the current map exposes the differences between loaded and server state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100