@remit/api-openapi-types 0.0.72 → 0.0.74

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/api-openapi-types",
-  "version": "0.0.72",
+  "version": "0.0.74",
   "type": "module",
   "main": "types.d.ts",
   "types": "types.d.ts",

package/types.d.ts

@@ -304,6 +304,10 @@ distinguishable from a network failure without parsing prose.
      * Where in a message a suggestion was read from. It is what a card says to explain itself, and it is what separates a suggestion carrying real iCalendar from one inferred out of prose.
      */
     export type CalendarSuggestionSource = "IcalendarPart" | "IcalendarAttachment" | "TextHeuristic";
+    /**
+     * The answer an invitation is added to a calendar with. It is written as the user's `ATTENDEE;PARTSTAT` on the stored event (RFC 5545 3.2.12) and becomes the suggestion's state.
+     */
+    export type CalendarInviteAnswer = "Accepted" | "Tentative";
     /**
      * System message flags defined in RFC 9051 Section 2.3.2 - MUST be supported by all servers
      */
@@ -4185,6 +4189,14 @@ garbage, which is the only thing the sweep needs to know.
        * Whether the bytes have arrived
        */
       state: OutboxAttachmentState;
+      /**
+       * Content-ID the body refers to this file by, as `cid:<contentId>`
+       */
+      contentId: String256;
+      /**
+       * URL the composer fetches the stored bytes from, the same /content route a received part is read through
+       */
+      contentUrl: string;
     }
     /**
      * Input for updating a draft outbox message
@@ -4273,6 +4285,10 @@ either way and cannot tell which it received.
        * Reserved size. The upload must carry exactly this many bytes.
        */
       sizeBytes: number;
+      /**
+       * Content-ID the body refers to this file by, as `cid:<contentId>`. A file the HTML body refers to goes out inline.
+       */
+      contentId: String256;
       /**
        * Where to PUT the raw bytes. Single use, one attachment, expires.
        */
@@ -5473,7 +5489,7 @@ and no message may make that change without them.
        */
       icalData: string;
       /**
-       * The `CalendarObject` that accepting this suggestion wrote. `""` until it is accepted — the named absent state, never a missing attribute — and the resource's id afterwards, so the card can link to the event it produced.
+       * The `CalendarObject` that accepting this suggestion wrote. `""` until it is accepted or answered tentatively — the named absent state, never a missing attribute — and the resource's id afterwards, so the card can link to the event it produced.
        */
       acceptedCalendarObjectId: string;
       createdAt: number;
@@ -5548,7 +5564,7 @@ and no message may make that change without them.
        */
       zoneCertainty: ZoneCertainty;
       /**
-       * The `CalendarObject` that accepting this suggestion wrote. `""` until it is accepted — the named absent state, never a missing attribute — and the resource's id afterwards, so the card can link to the event it produced.
+       * The `CalendarObject` that accepting this suggestion wrote. `""` until it is accepted or answered tentatively — the named absent state, never a missing attribute — and the resource's id afterwards, so the card can link to the event it produced.
        */
       acceptedCalendarObjectId: string;
       createdAt: number;
@@ -5562,6 +5578,10 @@ and no message may make that change without them.
        * Collection the accepted event is written into.
        */
       calendarId: UUID;
+      /**
+       * How the user answers. `Tentative` adds the event as a maybe. Refused with 400 on a `Cancel` suggestion, which has nothing to answer tentatively.
+       */
+      answer?: CalendarInviteAnswer;
     }
     /**
      * Body of `POST /calendar-suggestions/{suggestionId}/dismiss`.
@@ -8084,6 +8104,9 @@ same service function every other calendar write goes through — so a web
 edit and a native edit of that event cannot diverge. Accepting a `Cancel`
 suggestion writes `STATUS:CANCELLED` on the resource the same way.
 
+`answer: Tentative` writes the same resource with `PARTSTAT=TENTATIVE`
+and moves the suggestion to `Tentative` instead of `Accepted`.
+
 No reply is sent to the organizer. This endpoint sends no mail at all,
 and the card says so.
 
@@ -8092,7 +8115,8 @@ resource and returns the same suggestion, because both the resource id
 and the suggestion id are derived rather than minted.
 
 400 when the suggestion is not one that can be accepted — already
-declined, dismissed or superseded — or when its iCalendar will not parse.
+answered otherwise, dismissed or superseded — when a `Cancel` suggestion
+is answered `Tentative`, or when its iCalendar will not parse.
    */
   'acceptCalendarSuggestion'(
     parameters?: Parameters<Paths.AcceptCalendarSuggestion.PathParameters> | null,
@@ -8968,6 +8992,9 @@ same service function every other calendar write goes through — so a web
 edit and a native edit of that event cannot diverge. Accepting a `Cancel`
 suggestion writes `STATUS:CANCELLED` on the resource the same way.
 
+`answer: Tentative` writes the same resource with `PARTSTAT=TENTATIVE`
+and moves the suggestion to `Tentative` instead of `Accepted`.
+
 No reply is sent to the organizer. This endpoint sends no mail at all,
 and the card says so.
 
@@ -8976,7 +9003,8 @@ resource and returns the same suggestion, because both the resource id
 and the suggestion id are derived rather than minted.
 
 400 when the suggestion is not one that can be accepted — already
-declined, dismissed or superseded — or when its iCalendar will not parse.
+answered otherwise, dismissed or superseded — when a `Cancel` suggestion
+is answered `Tentative`, or when its iCalendar will not parse.
      */
     'post'(
       parameters?: Parameters<Paths.AcceptCalendarSuggestion.PathParameters> | null,
@@ -9256,6 +9284,7 @@ export type LabelAction = Components.Schemas.LabelAction;
 export type CalendarSuggestionState = Components.Schemas.CalendarSuggestionState;
 export type CalendarInviteMethod = Components.Schemas.CalendarInviteMethod;
 export type CalendarSuggestionSource = Components.Schemas.CalendarSuggestionSource;
+export type CalendarInviteAnswer = Components.Schemas.CalendarInviteAnswer;
 export type MessageSystemFlag = Components.Schemas.MessageSystemFlag;
 export type MessageKeywordFlag = Components.Schemas.MessageKeywordFlag;
 export type MailboxAttribute = Components.Schemas.MailboxAttribute;