Make history repository optionally support "edit" besides "view"

Created on 10 April 2022, about 3 years ago
Updated 16 May 2025, 3 days ago

Problem/Motivation

Imagine a mechanism to warn for concurrent edits, that on edit pages has some js that pings the server to signal "still editing", and gets back if another client set such a "soft-lock". This would benefit from a improved history repository to store the soft-locks.

Proposed resolution

Add "operation" and serialized "payload/data" to history repotitory.

Remaining tasks

- Decide if this better goes into history repository or be a separate thing
- do it

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task
Status

Postponed

Version

11.0 🔥

Component

history.module

Created by

🇩🇪Germany geek-merlin Freiburg, Germany

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024