nextcloud / nextcloud/tables

Notify support / indicate when rows updated + offer refresh

Open
#2,128 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement
Dominant language
JavaScript
Stars
214
Forks
52
Avg merge
1d 10h
Merged PRs (30d)
82

Description

Scenario

Alice has a table or view open, meanwhile Bob is modifying the content (could be changing, removing or adding a row).

Alice would like to know when content is modified and would like to have a possibility to refresh the data, without a full page reload, and with keeping temporary modifications (e.g. filters, sortings).

Implementation hints
  • In the backend, tables makes use of notify_push and informs about tables or views where content is modified
  • In front-end, tables registers a listener on this event
  • When a message comes, the user will be notified, that table/view content was changed
  • Furthermore, a button appears, that enables the user to reload that data of currently active table or view
Precondition

notify_push is enabled on the NC instance.

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 how the backend uses notify_push for table or view changes, then inspect where frontend tables registers a listener. Done means users are notified when content changes and can refresh the active table or view without a full page reload while retaining filters and sorting.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.