@remit/api-http-client 0.0.63 → 0.0.65

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/api-http-client",
-  "version": "0.0.63",
+  "version": "0.0.65",
   "type": "module",
   "exports": {
     ".": "./index.ts",

package/types.gen.ts

@@ -44,6 +44,10 @@ export type MicrosoftOAuthStartRequest = {
      * Optional email hint for the Microsoft login page
      */
     email?: string;
+    /**
+     * Services to request consent for. The authorization URL asks for the scopes these map to. Defaults to `#[Mail]`; refused when empty. Adding a service to a connected account is this same request carrying the full set the account should sync.
+     */
+    services?: Array<RemitImapAccountService>;
 };
 
 export type MicrosoftOAuthStartResponse = {
@@ -184,6 +188,10 @@ export type RemitImapAccountResponse = {
      * Services this account syncs. Never empty. A password account holds `Mail` alone. Every account written before this field existed holds `#[AccountService.Mail]`.
      */
     readonly syncedServices: Array<RemitImapAccountService>;
+    /**
+     * OAuth scopes the provider confirmed on the last consent, as full scope URIs. Empty on a password account. A Microsoft account can only select a service these scopes cover; one that lacks it goes back through POST /accounts/oauth/microsoft/start carrying that service.
+     */
+    readonly grantedScopes: Array<string>;
     /**
      * IMAP server hostname or IP address
      */
@@ -1882,6 +1890,10 @@ export type RemitImapMailboxResponse = {
      * The path a recorded rename is moving this folder to. Absent unless a rename is in flight or has just failed, which is what tells a create in flight from a rename in flight (D2, D3). `fullPath` stays the path the server holds throughout, so a failed rename is this field cleared rather than a subtree of paths restored. Invariant: non-null only while `syncStatus` is `pending` or `failed`.
      */
     pendingPath?: String512;
+    /**
+     * What the mail server said when it refused the last folder mutation, verbatim, so a folder in `failed` can say why. Total: the empty string whenever `syncStatus` is not `failed`, and on a failure the server gave no text for.
+     */
+    readonly syncFailureReason: string;
     /**
      * Denormalized list of IMAP SPECIAL-USE designations (RFC 6154). Populated from the same `\Sent`, `\Drafts`, etc. attributes the server reports during LIST. Stored on the row to avoid an N+1 join when listing mailboxes.
      */
@@ -4100,6 +4112,25 @@ export type MicrosoftOAuthOperationsMicrosoftOAuthStartData = {
 };
 
 export type MicrosoftOAuthOperationsMicrosoftOAuthStartErrors = {
+    /**
+     * The request was refused as malformed or contradictory. `code` is
+     * `invalid_request` where nothing more specific is known, and the refusal's own
+     * token where there is one.
+     *
+     * The calendar surface answers with the reason it read the request by:
+     * `invalid_window`, `invalid_scope`, `invalid_url_segment`, `url_segment_taken`,
+     * `unknown_time_zone` and `default_calendar_undeletable` on the collection and
+     * the query, and, for a VCALENDAR it could not accept,
+     * `malformed_icalendar`, `not_a_calendar`, `unsupported_component`, `no_event`,
+     * `no_master_event`, `multiple_master_events`, `missing_uid`, `mismatched_uid`,
+     * `missing_dt_start`, `backwards_end`, `invalid_date_time`,
+     * `invalid_recurrence_rule`, `missing_recurrence_id`, `not_recurring`,
+     * `unknown_occurrence` and `unmovable_recurrence_rule`.
+     *
+     * `errors` is present only when the request failed schema validation before any
+     * handler ran, and names every field that was refused.
+     */
+    400: ValidationError;
     /**
      * The request carried no usable credential. `code` is `unauthorized`.
      */