@remit/api-openapi-types 0.0.76 → 0.0.77

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/api-openapi-types",
-  "version": "0.0.76",
+  "version": "0.0.77",
   "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";
+    /**
+     * Whether an answered cancellation holds the calendar object this suggestion's answer wrote. A cancellation is terminal, so such an answer cannot be taken back.
+     */
+    export type CalendarAnswerOvertaken = "None" | "Cancellation";
     /**
      * 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.
      */
@@ -5581,6 +5585,10 @@ and no message may make that change without them.
        * The conversation holding `supersededByMessageId`, which is what the reading pane opens. `""` when this revision was not superseded, or when that message sits in no conversation any more.
        */
       supersededByThreadId: string;
+      /**
+       * Whether an answered cancellation holds the event this answer wrote. `Cancellation` means `reopen` answers 400.
+       */
+      answerOvertakenBy: CalendarAnswerOvertaken;
     }
     /**
      * Body of `POST /calendar-suggestions/{suggestionId}/accept`. Names the collection the event is written into; there is no default, because filing someone else's invitation into a calendar the user did not pick is a decision the server does not get to make.
@@ -7384,6 +7392,17 @@ declare namespace Paths {
       export type $401 = void;
     }
   }
+  namespace ReopenCalendarSuggestion {
+    export interface PathParameters {
+      suggestionId: Components.Schemas.UUID;
+    }
+    namespace Responses {
+      export type $200 = void;
+      export type $400 = void;
+      export type $404 = void;
+      export type $401 = void;
+    }
+  }
 }
 
 export interface OperationMethods {
@@ -8155,6 +8174,29 @@ is answered `Tentative`, or when its iCalendar will not parse.
     data?: Paths.DismissCalendarSuggestion.RequestBody,
     config?: AxiosRequestConfig
   ): OperationResponse<Paths.DismissCalendarSuggestion.Responses.$200>;
+  /**
+   * reopenCalendarSuggestion - Take an answer back. An accepted, tentative, declined or dismissed
+suggestion returns to `Pending`, so the card asks again. One
+transaction: the suggestion is settled `Pending` with
+`acceptedCalendarObjectId: ""`, and the calendar object an accept or a
+maybe wrote is removed with its occurrences and every remainder a
+this-and-following edit split off it in that calendar, unless another
+suggestion is still answered into that object; then the object stays with
+that answer. A sender rule written by
+`dismiss{muteSender}` stays; it is a rule of its own, edited where rules
+are.
+
+No mail is sent. Idempotent: a `Pending` suggestion is returned as it is.
+
+400 when the suggestion is `Superseded`, which a later revision retired,
+a `Cancel`, whose answer rewrote an event it cannot restore, or its
+`answerOvertakenBy` is `Cancellation`, because a cancellation is terminal.
+   */
+  'reopenCalendarSuggestion'(
+    parameters?: Parameters<Paths.ReopenCalendarSuggestion.PathParameters> | null,
+    data?: any,
+    config?: AxiosRequestConfig
+  ): OperationResponse<Paths.ReopenCalendarSuggestion.Responses.$200>;
 }
 
 export interface PathsDictionary {
@@ -9048,6 +9090,31 @@ is answered `Tentative`, or when its iCalendar will not parse.
       config?: AxiosRequestConfig
     ): OperationResponse<Paths.DismissCalendarSuggestion.Responses.$200>;
   };
+  ['/calendar-suggestions/{suggestionId}/reopen']: {
+    /**
+     * reopenCalendarSuggestion - Take an answer back. An accepted, tentative, declined or dismissed
+suggestion returns to `Pending`, so the card asks again. One
+transaction: the suggestion is settled `Pending` with
+`acceptedCalendarObjectId: ""`, and the calendar object an accept or a
+maybe wrote is removed with its occurrences and every remainder a
+this-and-following edit split off it in that calendar, unless another
+suggestion is still answered into that object; then the object stays with
+that answer. A sender rule written by
+`dismiss{muteSender}` stays; it is a rule of its own, edited where rules
+are.
+
+No mail is sent. Idempotent: a `Pending` suggestion is returned as it is.
+
+400 when the suggestion is `Superseded`, which a later revision retired,
+a `Cancel`, whose answer rewrote an event it cannot restore, or its
+`answerOvertakenBy` is `Cancellation`, because a cancellation is terminal.
+     */
+    'post'(
+      parameters?: Parameters<Paths.ReopenCalendarSuggestion.PathParameters> | null,
+      data?: any,
+      config?: AxiosRequestConfig
+    ): OperationResponse<Paths.ReopenCalendarSuggestion.Responses.$200>;
+  };
 }
 
 export type Client = OpenAPIClient<OperationMethods, PathsDictionary>;
@@ -9300,6 +9367,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 CalendarAnswerOvertaken = Components.Schemas.CalendarAnswerOvertaken;
 export type CalendarInviteAnswer = Components.Schemas.CalendarInviteAnswer;
 export type MessageSystemFlag = Components.Schemas.MessageSystemFlag;
 export type MessageKeywordFlag = Components.Schemas.MessageKeywordFlag;