@remit/api-openapi-spec 0.0.56 → 0.0.57
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/openapi.json +21 -0
- package/package.json +1 -1
package/openapi.json
CHANGED
|
@@ -1453,6 +1453,7 @@
|
|
|
1453
1453
|
},
|
|
1454
1454
|
"patch": {
|
|
1455
1455
|
"operationId": "MailboxDetailOperations_renameMailbox",
|
|
1456
|
+
"description": "Rename a folder, or dismiss a folder mutation that failed. `fullPath` records the rename target over the folder and everything under it; the folder keeps the path the mail server holds until the rename lands. A `fullPath` equal to the folder's current one is a dismissal: it clears a failed rename or delete and enqueues nothing. Refused with 400 for INBOX at either end, a name reserved for a system folder, and a name another folder already has; with 409 when a mutation is already in flight on the folder or on anything inside it.",
|
|
1456
1457
|
"parameters": [
|
|
1457
1458
|
{
|
|
1458
1459
|
"name": "accountId",
|
|
@@ -1482,6 +1483,16 @@
|
|
|
1482
1483
|
}
|
|
1483
1484
|
}
|
|
1484
1485
|
},
|
|
1486
|
+
"400": {
|
|
1487
|
+
"description": "The request was refused as malformed or contradictory. `code` is\n`invalid_request` where nothing more specific is known, and the refusal's own\ntoken where there is one.\n\nThe calendar surface answers with the reason it read the request by:\n`invalid_window`, `invalid_scope`, `invalid_url_segment`, `url_segment_taken`,\n`unknown_time_zone` and `default_calendar_undeletable` on the collection and\nthe query, and, for a VCALENDAR it could not accept,\n`malformed_icalendar`, `not_a_calendar`, `unsupported_component`, `no_event`,\n`no_master_event`, `multiple_master_events`, `missing_uid`, `mismatched_uid`,\n`missing_dt_start`, `backwards_end`, `invalid_date_time`,\n`invalid_recurrence_rule`, `missing_recurrence_id`, `not_recurring` and\n`unknown_occurrence`.\n\n`errors` is present only when the request failed schema validation before any\nhandler ran, and names every field that was refused.",
|
|
1488
|
+
"content": {
|
|
1489
|
+
"application/json": {
|
|
1490
|
+
"schema": {
|
|
1491
|
+
"$ref": "#/components/schemas/ValidationError"
|
|
1492
|
+
}
|
|
1493
|
+
}
|
|
1494
|
+
}
|
|
1495
|
+
},
|
|
1485
1496
|
"401": {
|
|
1486
1497
|
"description": "The request carried no usable credential. `code` is `unauthorized`.",
|
|
1487
1498
|
"content": {
|
|
@@ -1511,6 +1522,16 @@
|
|
|
1511
1522
|
}
|
|
1512
1523
|
}
|
|
1513
1524
|
}
|
|
1525
|
+
},
|
|
1526
|
+
"409": {
|
|
1527
|
+
"description": "The request contradicts the state the resource is in. `code` is `conflict`\nunless the refusal names its own — see `FolderRoleConflict`,\n`MessagePlacementConflict` and `ConfigImportConflict`.",
|
|
1528
|
+
"content": {
|
|
1529
|
+
"application/json": {
|
|
1530
|
+
"schema": {
|
|
1531
|
+
"$ref": "#/components/schemas/ApiError"
|
|
1532
|
+
}
|
|
1533
|
+
}
|
|
1534
|
+
}
|
|
1514
1535
|
}
|
|
1515
1536
|
},
|
|
1516
1537
|
"requestBody": {
|