basalt / drives/src / DriveNotificationOutcome

Interface: DriveNotificationOutcome

Defined in: drives/src/notifications.ts:134

Properties

challenge?

> optional challenge?: string

Defined in: drives/src/notifications.ts:136

Answer the provider with this body and content-type: text/plain, then stop.

---

connections

> connections: readonly DriveConnection[]

Defined in: drives/src/notifications.ts:146

The connections the notification concerns — empty when nothing matched.

A list, not one connection: a Dropbox notification names accounts, and one Dropbox account can be connected several times (two labels in one tenant, or the same account connected by two tenants). Phase 1 returned a single connection, which would have silently synced one of them and left the rest stale.

---

reason?

> optional reason?: "challenge" | "no-change" | "replay" | "unmatched"

Defined in: drives/src/notifications.ts:157

Why nothing is going to happen, when shouldSync is false.

unmatched is a verified notification that concerns no connection we hold. It is deliberately not an error: answering it differently from a matched one turns the endpoint into an oracle for "is this account/channel connected here". The app may log it; the HTTP response must not differ.

---

shouldSync

> shouldSync: boolean

Defined in: drives/src/notifications.ts:148

Whether the app should schedule a sync.