@remit/api-openapi-spec 0.0.75 → 0.0.77

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.
Files changed (2) hide show
  1. package/openapi.json +32 -2
  2. package/package.json +1 -1
package/openapi.json CHANGED
@@ -4881,7 +4881,17 @@
4881
4881
  }
4882
4882
  },
4883
4883
  "404": {
4884
- "description": "Nothing answers to this address, or the caller may not learn that something does. `code` is `not_found`.",
4884
+ "description": "No message answers to this id, or the caller may not learn that one does.\n`code` is `not_found`, or `message_gone_from_server` when the mail server no\nlonger holds the message at its UID — another client expunged it or moved it\naway before its body was stored. That answer carries `details.messageId`.",
4885
+ "content": {
4886
+ "application/json": {
4887
+ "schema": {
4888
+ "$ref": "#/components/schemas/ApiError"
4889
+ }
4890
+ }
4891
+ }
4892
+ },
4893
+ "409": {
4894
+ "description": "The same flat 409 body, for a message whose folder and uid do not name the same message.\n\n`code: \"message_placement_unsettled\"` — the message is mid-move, so its row names the destination folder while its uid still belongs to the source; acting on that pair would hit whatever the destination holds at that uid. `details` carries `accountId`, `messageId` and `reason`, one of: `in_flight` (the move is still running, and the same request succeeds once it confirms) or `unverified` (the move gave up without confirming, so where the message sits is unknown until the folder is resynced).",
4885
4895
  "content": {
4886
4896
  "application/json": {
4887
4897
  "schema": {
@@ -5113,7 +5123,17 @@
5113
5123
  }
5114
5124
  },
5115
5125
  "404": {
5116
- "description": "Nothing answers to this address, or the caller may not learn that something does. `code` is `not_found`.",
5126
+ "description": "No message answers to this id, or the caller may not learn that one does.\n`code` is `not_found`, or `message_gone_from_server` when the mail server no\nlonger holds the message at its UID — another client expunged it or moved it\naway before its body was stored. That answer carries `details.messageId`.",
5127
+ "content": {
5128
+ "application/json": {
5129
+ "schema": {
5130
+ "$ref": "#/components/schemas/ApiError"
5131
+ }
5132
+ }
5133
+ }
5134
+ },
5135
+ "409": {
5136
+ "description": "The same flat 409 body, for a message whose folder and uid do not name the same message.\n\n`code: \"message_placement_unsettled\"` — the message is mid-move, so its row names the destination folder while its uid still belongs to the source; acting on that pair would hit whatever the destination holds at that uid. `details` carries `accountId`, `messageId` and `reason`, one of: `in_flight` (the move is still running, and the same request succeeds once it confirms) or `unverified` (the move gave up without confirming, so where the message sits is unknown until the folder is resynced).",
5117
5137
  "content": {
5118
5138
  "application/json": {
5119
5139
  "schema": {
@@ -7959,6 +7979,7 @@
7959
7979
  "summary",
7960
7980
  "dtStart",
7961
7981
  "dtEnd",
7982
+ "endsAtUtc",
7962
7983
  "allDay",
7963
7984
  "location",
7964
7985
  "organizer",
@@ -8080,6 +8101,15 @@
8080
8101
  "description": "Projection of the VEVENT's effective end as an ISO 8601 date-time with zone offset, resolved from DTEND or from DTSTART + DURATION. An event with neither ends when it starts (RFC 5545 3.6.1).",
8081
8102
  "readOnly": true
8082
8103
  },
8104
+ "endsAtUtc": {
8105
+ "allOf": [
8106
+ {
8107
+ "$ref": "#/components/schemas/String64"
8108
+ }
8109
+ ],
8110
+ "description": "The UTC instant (ISO 8601, `Z` suffix) after which nothing of this event remains to attend: the end of the last occurrence of a bounded series, `9999-12-31T23:59:59Z` for an open-ended one. Unlike `dtEnd` it compares correctly as a string across offsets, which is what lets a list drop events that are over.",
8111
+ "readOnly": true
8112
+ },
8083
8113
  "allDay": {
8084
8114
  "type": "boolean",
8085
8115
  "description": "Whether DTSTART is a DATE rather than a DATE-TIME (RFC 5545 3.3.4) — an all-day or multi-day event, whose end is exclusive.",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@remit/api-openapi-spec",
3
- "version": "0.0.75",
3
+ "version": "0.0.77",
4
4
  "description": "Remit API OpenAPI 3 document, generated from TypeSpec.",
5
5
  "exports": {
6
6
  ".": "./openapi.json",