nextcloud / nextcloud/text

Update content of unchanged file when changed on the server

Open
#7,753 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: sync
Dominant language
JavaScript
Stars
659
Forks
133
Avg merge
1d 20h
Merged PRs (30d)
110

Description

Follow up to #4078

Is your feature request related to a problem? Please describe.
When reverting to a previous version or changing the content of a file on the server via another means we currently make the editor read only and display

Image

Instead it would be nice to load the new content and keep the editor editable.

Describe the solution you'd like

We already detect that the editing session was cleared. Reload the editor fetching the new file and creating a new editing session.

Describe alternatives you've considered

Automatically reloading the entire page feels too intrusive.
Better wording of the error message would be a start but still leaves the user with one option we expect them to click.

Additional context

We might want to still show a message indicating that the content updated - but we would also not do that if the content was updated inside another text editor session. So I think it would be

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the existing handling for a cleared editing session and how the editor currently becomes read-only when server content changes. Verify how a fresh file fetch and editing session are initiated, then confirm that the editor remains editable with the server's new content without reloading the page.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.