@remit/api-openapi-types 0.0.61 → 0.0.62

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/package.json +1 -1
  2. package/types.d.ts +33 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@remit/api-openapi-types",
3
- "version": "0.0.61",
3
+ "version": "0.0.62",
4
4
  "type": "module",
5
5
  "main": "types.d.ts",
6
6
  "types": "types.d.ts",
package/types.d.ts CHANGED
@@ -597,11 +597,9 @@ unless the refusal names its own — see `FolderRoleConflict`,
597
597
  details?: Record;
598
598
  }
599
599
  /**
600
- * The same flat 409 body as `FolderRoleConflict`, with one code only this endpoint can answer with.
600
+ * The same flat 409 body as `FolderRoleConflict`, with the codes only this endpoint can answer with.
601
601
 
602
602
  `code: "folder_role_unresolved"` — as everywhere else, with `details` carrying `role`, `accountId` and `reason`.
603
-
604
- `code: "mailbox_not_settled"` — the mailbox being appointed is still being created or deleted on the mail server, so it cannot yet hold a role. `details` carries `mailboxId` and `syncStatus`. Clearing a role is never refused this way.
605
603
  */
606
604
  export interface AppointFolderRoleConflict {
607
605
  statusCode: 409;
@@ -618,6 +616,28 @@ unless the refusal names its own — see `FolderRoleConflict`,
618
616
  */
619
617
  details?: Record;
620
618
  }
619
+ /**
620
+ * The write binds a durable reference — a role appointment, a filter's move target, a message's destination — to a folder whose own mutation has not settled, so the reference would point at something that may never exist.
621
+
622
+ `code: "mailbox_not_settled"` — `details` carries `mailboxId` and `syncStatus`, one of `pending` (the mail server has not confirmed the folder yet), `deleting` (it is on its way out) or `failed` (its last rename or delete did not land, and the user has a retry or a dismissal to make first). Clearing a reference is never refused this way, and neither is moving mail *out of* such a folder.
623
+
624
+ 422 rather than a second 409: 409 means somebody else is changing this folder right now and the client should refresh, which is different copy and a different remedy.
625
+ */
626
+ export interface MailboxNotSettled {
627
+ statusCode: 422;
628
+ /**
629
+ * Stable token naming the refusal. Branch on this, never on `message`.
630
+ */
631
+ code: string;
632
+ /**
633
+ * Human-readable error message
634
+ */
635
+ message: string;
636
+ /**
637
+ * Additional error details
638
+ */
639
+ details?: Record;
640
+ }
621
641
  /**
622
642
  * The condition the request stated is no longer true. Answered when an
623
643
  `If-Match` names an etag the stored resource no longer carries: somebody else
@@ -6399,6 +6419,8 @@ declare namespace Paths {
6399
6419
  }
6400
6420
  namespace Responses {
6401
6421
  export type $204 = void;
6422
+ export type $400 = void;
6423
+ export type $409 = void;
6402
6424
  export type $404 = void;
6403
6425
  export type $403 = void;
6404
6426
  export type $401 = void;
@@ -6413,6 +6435,7 @@ declare namespace Paths {
6413
6435
  namespace Responses {
6414
6436
  export type $200 = void;
6415
6437
  export type $409 = void;
6438
+ export type $422 = void;
6416
6439
  export type $404 = void;
6417
6440
  export type $403 = void;
6418
6441
  export type $401 = void;
@@ -6440,6 +6463,7 @@ declare namespace Paths {
6440
6463
  namespace Responses {
6441
6464
  export type $200 = void;
6442
6465
  export type $400 = void;
6466
+ export type $422 = void;
6443
6467
  export type $404 = void;
6444
6468
  export type $403 = void;
6445
6469
  export type $401 = void;
@@ -6464,6 +6488,7 @@ declare namespace Paths {
6464
6488
  export type RequestBody = Components.Schemas.UpdateFilterInput;
6465
6489
  namespace Responses {
6466
6490
  export type $200 = void;
6491
+ export type $422 = void;
6467
6492
  export type $404 = void;
6468
6493
  export type $403 = void;
6469
6494
  export type $401 = void;
@@ -7106,6 +7131,7 @@ declare namespace Paths {
7106
7131
  namespace Responses {
7107
7132
  export type $200 = void;
7108
7133
  export type $409 = void;
7134
+ export type $422 = void;
7109
7135
  export type $404 = void;
7110
7136
  export type $403 = void;
7111
7137
  export type $401 = void;
@@ -7116,6 +7142,7 @@ declare namespace Paths {
7116
7142
  namespace Responses {
7117
7143
  export type $200 = void;
7118
7144
  export type $409 = void;
7145
+ export type $422 = void;
7119
7146
  export type $404 = void;
7120
7147
  export type $403 = void;
7121
7148
  export type $401 = void;
@@ -7320,7 +7347,7 @@ export interface OperationMethods {
7320
7347
  config?: AxiosRequestConfig
7321
7348
  ): OperationResponse<Paths.RenameMailbox.Responses.$200>;
7322
7349
  /**
7323
- * deleteMailbox
7350
+ * deleteMailbox - Record a delete intent for a folder. The folder stays listed, marked as being deleted, until the mail server confirms it and its mail goes with it. Refused with 400 for INBOX, for a folder with folders inside it, and for a folder a filter or a canonical role is bound to — the message names each binding; with 409 when a mutation is already in flight on it.
7324
7351
  */
7325
7352
  'deleteMailbox'(
7326
7353
  parameters?: Parameters<Paths.DeleteMailbox.PathParameters> | null,
@@ -8106,7 +8133,7 @@ export interface PathsDictionary {
8106
8133
  config?: AxiosRequestConfig
8107
8134
  ): OperationResponse<Paths.RenameMailbox.Responses.$200>;
8108
8135
  /**
8109
- * deleteMailbox
8136
+ * deleteMailbox - Record a delete intent for a folder. The folder stays listed, marked as being deleted, until the mail server confirms it and its mail goes with it. Refused with 400 for INBOX, for a folder with folders inside it, and for a folder a filter or a canonical role is bound to — the message names each binding; with 409 when a mutation is already in flight on it.
8110
8137
  */
8111
8138
  'delete'(
8112
8139
  parameters?: Parameters<Paths.DeleteMailbox.PathParameters> | null,
@@ -8874,6 +8901,7 @@ export type ForbiddenError = Components.Schemas.ForbiddenError;
8874
8901
  export type NoContent = Components.Schemas.NoContent;
8875
8902
  export type FolderRoleConflict = Components.Schemas.FolderRoleConflict;
8876
8903
  export type AppointFolderRoleConflict = Components.Schemas.AppointFolderRoleConflict;
8904
+ export type MailboxNotSettled = Components.Schemas.MailboxNotSettled;
8877
8905
  export type PreconditionFailedError = Components.Schemas.PreconditionFailedError;
8878
8906
  export type DeleteMessagesConflict = Components.Schemas.DeleteMessagesConflict;
8879
8907
  export type MessagePlacementConflict = Components.Schemas.MessagePlacementConflict;