nextcloud / nextcloud/tables

OCS Resolve API issues (missing ID, verbose response)

Open
#1,555 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: api needs info
Dominant language
JavaScript
Stars
214
Forks
52
Avg merge
1d 10h
Merged PRs (30d)
82

Description

Is your feature request related to a problem? Please describe.

The OCS Resolve endoint (GET https://example.com/ocs/v2.php/references/resolve?reference=https%3A%2F%2Fexample.com%2Findex.php%2Fapps%2Ftables%2F%23%2Ftable%2F10) currently returns a richObject property, that doesn't actually satisfy me.

First of all, it includes all data from that table. Given this endpoint gets hit when a user searches for anything, that seems to be a bit too verbose to me.

Also: I expected (and require) the most obvious information: the ID of the object. Sure, I could parse it from the URL, but what if the UI changes at some point in the time? No, I'd like the ID to be present in the response if possible 🙂

Describe the solution you'd like

Drop the rows property, the summarizing row count is enough, add the id property.

Describe alternatives you've considered

No response

Additional context

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

Start by tracing the OCS Resolve endpoint at GET /ocs/v2.php/references/resolve and inspect how its response is assembled. Confirm where the richObject data is produced, then verify the response retains the row count while exposing the object ID and omitting rows. Exercise the endpoint with the reference URL from the issue to check the final payload.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.