OCS-API for columns not working
Open
Nobody has claimed this yet.
1. to develop
bug
feature: api
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Steps to reproduce
- install current beta 0.7.0-beta.2 of tables
- post a column to an existing table via OCS-API:
/ocs/v2.php/apps/tables/api/2/columns/text, alternatively to/ocs/v2.php/apps/tables/api/2/columns/datetime. - Open the table in the browser.
Expected behavior
Table is shown with the newly created column(s)
Actual behavior
Table is not loading, the browser console has the error Unhandled Promise Rejection: Error: text is not a valid column type!
Tables app version
0.7.0-beta.2
Browser
Safari 17.3
Client operating system
MacOS
Operating system
No response
Web server
Apache
PHP engine version
PHP 8.2
Database
MariaDB
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the OCS-API column endpoints /ocs/v2.php/apps/tables/api/2/columns/text and /ocs/v2.php/apps/tables/api/2/columns/datetime on version 0.7.0-beta.2, then inspect the column-type handling indicated by the browser error. Done means a table remains loadable after either column is created and the console no longer reports that text is an invalid column type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100