nextcloud / nextcloud/tables

Omitting data while `PUT`ting a row does not delete the data

Open
#297 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Steps to reproduce
  1. Create a table with columns A and B
  2. PUT the row with only one value for A
Expected behavior

Expected that B gets deleted

Actual behavior

B still exists and has the same value as before

Tables app version

0.5.0

Browser

No response

Client operating system

No response

Operating system

No response

Web server

None

PHP engine version

None

Database

None

Additional info

Not sure whether this actually a bug or actually the solution for #265. However, this was not clear to me, so maybe this should at least be documented in the API description.

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 reviewing the Tables API description and the PUT-row handling for the reproduction using columns A and B, then compare the behavior with issue #265. Done means the intended treatment of an omitted column is decided and either implemented with coverage or clearly documented in the API.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.