nextcloud / nextcloud/tables

Wrong date of update of views

Open
#2,698 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
JavaScript
Stars
214
Forks
52
Avg merge
1d 10h
Merged PRs (30d)
82

Description

Steps to reproduce

Views have several attributes shown before the header, which include the Last modification time column. Its value is misleading, as views are not independent items, but rather a filtered values of the dates stored in a table. So, if I change something in a table, it is changed in a linked view/views, but the date is not changed. It can be only changed if I change the value stored in the table specifically from the views window. That is not correct.

  1. Have a table with some views, which filters data from the table, eg not showing some columns.
  2. Change the value in the table.
  3. Observe that the Last update time is not changed.
Expected behavior

The Last update time should reflect the changes in data, but not in a view. So, if I change the value in the table the date of update in values should be changed properly.

Actual behavior

The update time in views is not updated if changes are made in the table, but not a view.

Tables app version

No response

Browser

No response

Client operating system

No response

Operating system

No response

Web server

None

PHP engine version

None

Database

None

Additional info

No response

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

No file, test, browser, or version is named. Start by tracing how the Tables app computes and displays a view's Last modification time, then compare updates made in the source table with updates made through a view. Done means the displayed time changes for source-table data updates while remaining appropriate for view-definition changes, with regression coverage if the existing test structure supports it.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.