Figure out a way to handle simultaneous edits
Open
Nobody has claimed this yet.
hold
suggestion
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
Especially text bodies. Should we lock contexts? Or have some kind of versioning?
Nice things we can do:
- Lock page when someone edits
- Allow others who want to edit that page to ping that user or send a message to them
- If you're the locking user, flash that tab or view diffs
- Save drafts while writing
Suggested solution - listen to updates on that specific model and display the change to the user and let them handle it.
Like so:
- User starts to edit something
- Another user edits and saves
- Update will be pushed to the first user
- Frontend warns about the change and asks me if i want to view the diff & merge
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
No files, tests, or entry points are named. Start by mapping how edits to the affected model reach other users, then compare locking, versioning, and pushed-update approaches. Done means concurrent edits are detected and the first user can be warned, view the change, and choose how to proceed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100