You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/docs/openapi-v2-tables.json
+14-4Lines changed: 14 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -270,7 +270,7 @@
270
270
"delete": {
271
271
"operationId": "deleteTable",
272
272
"summary": "Delete Table",
273
-
"description": "Delete a table. Returns the id of the deleted table.",
273
+
"description": "Delete a table. Returns the id and an explicit deletion confirmation.",
274
274
"tags": ["Tables"],
275
275
"x-codeSamples": [
276
276
{
@@ -333,7 +333,7 @@
333
333
"patch": {
334
334
"operationId": "updateTable",
335
335
"summary": "Update Table",
336
-
"description": "Rename a table and/or move it between folders. Provide at least one of `name` or `folderPath`. Each field is applied independently, so one request can rename and move at once, and the response reflects every applied change.\n\nBoth fields need workspace write.\n\n**Lock flags are read-only here.** A table's `locks` are returned on the table resource and enforced on every write (a locked verb returns 423), but they cannot be changed through the API — a write-level key must not be able to clear the guard placed there to stop it. Changing a lock is a first-party workspace-admin action. A request carrying `locks` is rejected with 400 rather than silently ignored.\n\n**Partial-success semantics.** The two operations commit independently, so this endpoint is not atomic. Everything that can be *rejected* — the body shape, folder existence — is validated before the first write, so a rejected request changes nothing. If a genuine fault (a lost race, the table deleted mid-request, a database error) fails the later operation after the earlier one has committed, the response is an error whose `error.details.applied` lists the operations that are nevertheless live (`\"name\"`, `\"folderPath\"`). The field is absent when nothing was applied, so its presence always means \"these changes took effect despite the error\" — re-read the table to confirm before retrying.",
336
+
"description": "Rename a table, edit its description, and/or move it between folders. Provide at least one of `name`, `description`, or `folderPath`. Each field is applied independently, so one request can combine changes and the response reflects every applied change.\n\nAll three fields need workspace write.\n\n**Lock flags are read-only here.** A table's `locks` are returned on the table resource and enforced on every write (a locked verb returns 423), but they cannot be changed through the API — a write-level key must not be able to clear the guard placed there to stop it. Changing a lock is a first-party workspace-admin action. A request carrying `locks` is rejected with 400 rather than silently ignored.\n\n**Partial-success semantics.** The operations commit independently, so this endpoint is not atomic. Everything that can be *rejected* — the body shape, folder existence — is validated before the first write, so a rejected request changes nothing. If a genuine fault (a lost race, the table deleted mid-request, a database error) fails a later operation after an earlier one has committed, the response is an error whose `error.details.applied` lists the operations that are nevertheless live (`\"name\"`, `\"description\"`, `\"folderPath\"`). The field is absent when nothing was applied, so its presence always means \"these changes took effect despite the error\" — re-read the table to confirm before retrying.",
337
337
"tags": ["Tables"],
338
338
"x-codeSamples": [
339
339
{
@@ -4976,11 +4976,16 @@
4976
4976
"properties": {
4977
4977
"data": {
4978
4978
"type": "object",
4979
-
"required": ["id"],
4979
+
"required": ["id", "deleted"],
4980
4980
"properties": {
4981
4981
"id": {
4982
4982
"type": "string",
4983
4983
"description": "The id of the deleted table."
4984
+
},
4985
+
"deleted": {
4986
+
"type": "boolean",
4987
+
"const": true,
4988
+
"description": "Confirms the table was deleted."
4984
4989
}
4985
4990
}
4986
4991
}
@@ -5301,7 +5306,7 @@
5301
5306
},
5302
5307
"UpdateTableBody": {
5303
5308
"type": "object",
5304
-
"description": "Rename and/or move a table. Every field beyond `workspaceId` is optional, but at least one must be present. Lock flags are read-only on this API and are not accepted here.",
5309
+
"description": "Rename, edit the description, and/or move a table. Every field beyond `workspaceId` is optional, but at least one must be present. Lock flags are read-only on this API and are not accepted here.",
5305
5310
"required": ["workspaceId"],
5306
5311
"properties": {
5307
5312
"workspaceId": {
@@ -5314,6 +5319,11 @@
5314
5319
"minLength": 1,
5315
5320
"description": "New table name."
5316
5321
},
5322
+
"description": {
5323
+
"type": ["string", "null"],
5324
+
"maxLength": 500,
5325
+
"description": "New table description, or null to clear it."
5326
+
},
5317
5327
"folderPath": {
5318
5328
"type": "string",
5319
5329
"description": "Canonical containing-folder path. `/` is the workspace root."
0 commit comments