decaporg / decaporg/decap-cms

Concurrent editing

Open
#277 7 comments 8 reactions 0 assignees View on GitHub
area: collaboration area: ui/editor kind: discussion kind: feature pinned
Dominant language
JavaScript
Stars
19.4k
Forks
3.1k
Avg merge
1d 14h
Merged PRs (30d)
9

Description

**- Do you want to request a *feature* or report a *bug*?**

Feature

**- What is the current behavior?**

Right now I have to verbalize if I am making changes on something that another person may be making changes on... this is very confusing and I could see it leading to problems.

**- What is the expected behavior?**

Not sure what the best fix would be.. a notification of _currently be edited by NAME_ would be helpful to know who to go to. Or when you go to *SAVE* it tells you that's not the most updated version? But then that could cause issues with edits I may have made and then would potentially loose.. I'd be wary against any roadblocks because if someone is editing (but not actively) then that would cause a bottleneck.

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by clarifying which concurrent-editing behavior is wanted—editing notifications, save-time conflict detection, or another approach—and define the accepted behavior before implementation; the issue does not currently establish what done looks like.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.