nextcloud / nextcloud/tables

deleting one option of a multiple options column rather hides itself and other entries plus maybe reuses their former "base" for replacements and supplements

Open
#727 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Steps to reproduce
  1. Create a table which has the multiple selection type in any column
  2. Add a row with multiple options in a cell which is part of that column
  3. Delete one of the options which were predefined in step 1 by deleting it from the selectable options in the edit menu
  4. Add a new option in the same edit menu mentioned in step 3
Expected behavior

The option should be instantly and permanently deleted in every row where this option has been chosen and the options in the edit menu aswell. A row with one or more remaining options should still show these. And when adding (another) option a "whole new" option should be created.

Actual behavior

The chosen option remains visible until one clicks somewhere else and then back on the table or view, however the adding of an option is instantly visible. (Regardless whether of looking at a view or the "main page" of the table; showing the data and the views.)

As soon as one option is removed from the edit menu of the multiple selection column all cells in the rows that had chosen this option can no longer be edited and the remaining options within the cells are no longer visible.

When another option will be added later at the same "position", it will automatically be re-added to the rows, that lost an option before. Even if the option got a completly new name. The cells become editable and visible again, but it can cause confusion, because every new option is treated as a replacement for the deleted one and not a supplement for the bunch of all the other options.

Tables app version

0.6.4

Browser

Firefox 120.0

Client operating system

No response

Operating system

Debian

Web server

Apache

PHP engine version

PHP 8.1

Database

MariaDB

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 source file, test, or entry point is named. Start by reproducing the multiple-selection option deletion and replacement steps in the Tables app with the reported stack, then trace the option and cell behavior until you can verify that deleted choices disappear, remaining choices stay visible and editable, and newly added options do not restore deleted values.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, mariadb, php
Domain
database, full-stack
Issue type
Bug
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.