nextcloud / nextcloud/deck

Provide a working example of API usage to update a cards details

Open
#4,106 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature: api question
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

When using the API to create a card it seems not yet to be possible to add all details while creating the card - details have to be added in a second step.

To Reproduce
use curl in PHP to set a due date (which is described differently in the API doc compared to the request the browser does when using the GUI: "duedate": "2019-12-24T19:29:30+00:00" in the doc, duedate = "2022-10-07T02:20:00.000Z", the tzdata is formed different).

Expected behavior
Updated card with the due date.

Not clear from doc: do all fields have to be set in this PUT-request? Do you have to submit the title again, even if not changed?
I get a 400 bad request in ~50 different code "ideas" I tried to use :)

Client details:

  • OS: Linux on GUI, Linux on cli
  • Browser Firefox, cURL
  • Version [e.g. 22]
  • Device:
Server details

Where did you install Nextcloud from:
cli

NC Version: 21.0.9
Deck version: 1.4.8
PHP: Version: 7.4.10
DB: 10.5.5 mariadb

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 API documentation and the curl/PHP request described in the issue, then compare its due-date format with the browser request from the GUI. Document a working card-update example and clarify whether unchanged fields such as the title are required; done means the example successfully updates a due date without a 400 response.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
api, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.