@remit/api-http-client 0.0.63 → 0.0.64
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.
- package/package.json +1 -1
- package/types.gen.ts +27 -0
package/package.json
CHANGED
package/types.gen.ts
CHANGED
|
@@ -44,6 +44,10 @@ export type MicrosoftOAuthStartRequest = {
|
|
|
44
44
|
* Optional email hint for the Microsoft login page
|
|
45
45
|
*/
|
|
46
46
|
email?: string;
|
|
47
|
+
/**
|
|
48
|
+
* 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.
|
|
49
|
+
*/
|
|
50
|
+
services?: Array<RemitImapAccountService>;
|
|
47
51
|
};
|
|
48
52
|
|
|
49
53
|
export type MicrosoftOAuthStartResponse = {
|
|
@@ -184,6 +188,10 @@ export type RemitImapAccountResponse = {
|
|
|
184
188
|
* Services this account syncs. Never empty. A password account holds `Mail` alone. Every account written before this field existed holds `#[AccountService.Mail]`.
|
|
185
189
|
*/
|
|
186
190
|
readonly syncedServices: Array<RemitImapAccountService>;
|
|
191
|
+
/**
|
|
192
|
+
* 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.
|
|
193
|
+
*/
|
|
194
|
+
readonly grantedScopes: Array<string>;
|
|
187
195
|
/**
|
|
188
196
|
* IMAP server hostname or IP address
|
|
189
197
|
*/
|
|
@@ -4100,6 +4108,25 @@ export type MicrosoftOAuthOperationsMicrosoftOAuthStartData = {
|
|
|
4100
4108
|
};
|
|
4101
4109
|
|
|
4102
4110
|
export type MicrosoftOAuthOperationsMicrosoftOAuthStartErrors = {
|
|
4111
|
+
/**
|
|
4112
|
+
* The request was refused as malformed or contradictory. `code` is
|
|
4113
|
+
* `invalid_request` where nothing more specific is known, and the refusal's own
|
|
4114
|
+
* token where there is one.
|
|
4115
|
+
*
|
|
4116
|
+
* The calendar surface answers with the reason it read the request by:
|
|
4117
|
+
* `invalid_window`, `invalid_scope`, `invalid_url_segment`, `url_segment_taken`,
|
|
4118
|
+
* `unknown_time_zone` and `default_calendar_undeletable` on the collection and
|
|
4119
|
+
* the query, and, for a VCALENDAR it could not accept,
|
|
4120
|
+
* `malformed_icalendar`, `not_a_calendar`, `unsupported_component`, `no_event`,
|
|
4121
|
+
* `no_master_event`, `multiple_master_events`, `missing_uid`, `mismatched_uid`,
|
|
4122
|
+
* `missing_dt_start`, `backwards_end`, `invalid_date_time`,
|
|
4123
|
+
* `invalid_recurrence_rule`, `missing_recurrence_id`, `not_recurring`,
|
|
4124
|
+
* `unknown_occurrence` and `unmovable_recurrence_rule`.
|
|
4125
|
+
*
|
|
4126
|
+
* `errors` is present only when the request failed schema validation before any
|
|
4127
|
+
* handler ran, and names every field that was refused.
|
|
4128
|
+
*/
|
|
4129
|
+
400: ValidationError;
|
|
4103
4130
|
/**
|
|
4104
4131
|
* The request carried no usable credential. `code` is `unauthorized`.
|
|
4105
4132
|
*/
|