@bevel-software/platform-core-backend 0.31.0 → 0.32.0

package/dist/shared/listener-seam.js

@@ -0,0 +1,42 @@
+/**
+ * The one way core runs the notification listeners a deployment registers
+ * on a seam (an account invited, a change request opened): every listener
+ * in registration order, each awaited, the channels that reached somebody
+ * collected in that order, a failure logged and counted as "did not" so the
+ * event's own effect — the account made, the request opened — stands
+ * whatever the listeners do. A seam wraps one of these per event and keeps
+ * its own typed registration method, so the rule above is written once.
+ */
+export class ListenerSeam {
+    log;
+    failed;
+    listeners = [];
+    /**
+     * @param log Where a failed listener is reported.
+     * @param failed The line logged for one, said in the seam's own terms
+     *   ("an account-invited listener failed; the person was not notified by it:").
+     */
+    constructor(log, failed) {
+        this.log = log;
+        this.failed = failed;
+    }
+    add(listener) {
+        this.listeners.push(listener);
+    }
+    /** Run every listener in registration order; the channels that reached somebody, in that order. */
+    async run(event) {
+        const notified = [];
+        for (const listener of this.listeners) {
+            try {
+                const channel = await listener(event);
+                if (channel !== null && channel !== '')
+                    notified.push(channel);
+            }
+            catch (err) {
+                this.log.error(this.failed, { err });
+            }
+        }
+        return notified;
+    }
+}
+//# sourceMappingURL=listener-seam.js.map

package/dist/shared/listener-seam.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"listener-seam.js","sourceRoot":"","sources":["../../src/shared/listener-seam.ts"],"names":[],"mappings":"AAYA;;;;;;;;GAQG;AACH,MAAM,OAAO,YAAY;IASJ;IACA;IATF,SAAS,GAA2B,EAAE,CAAC;IAExD;;;;OAIG;IACH,YACmB,GAAY,EACZ,MAAc;QADd,QAAG,GAAH,GAAG,CAAS;QACZ,WAAM,GAAN,MAAM,CAAQ;IAC9B,CAAC;IAEJ,GAAG,CAAC,QAA8B;QAChC,IAAI,CAAC,SAAS,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC;IAChC,CAAC;IAED,mGAAmG;IACnG,KAAK,CAAC,GAAG,CAAC,KAAQ;QAChB,MAAM,QAAQ,GAAa,EAAE,CAAC;QAC9B,KAAK,MAAM,QAAQ,IAAI,IAAI,CAAC,SAAS,EAAE,CAAC;YACtC,IAAI,CAAC;gBACH,MAAM,OAAO,GAAG,MAAM,QAAQ,CAAC,KAAK,CAAC,CAAC;gBACtC,IAAI,OAAO,KAAK,IAAI,IAAI,OAAO,KAAK,EAAE;oBAAE,QAAQ,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC;YACjE,CAAC;YAAC,OAAO,GAAG,EAAE,CAAC;gBACb,IAAI,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,MAAM,EAAE,EAAE,GAAG,EAAE,CAAC,CAAC;YACvC,CAAC;QACH,CAAC;QACD,OAAO,QAAQ,CAAC;IAClB,CAAC;CACF"}

package/migrations/0019_oauth_token_rotated_at.sql

@@ -0,0 +1,7 @@
+-- When a refresh of the row's refresh token minted its successor. Rotation
+-- sets it; a revoke never does, so the two are told apart: a rotated row's
+-- access token still verifies until its own expiry, and its refresh token is
+-- honoured once more within the reuse grace, while a revoked row does neither
+-- (see `exchangeRefreshToken` in bevel-oauth-provider.ts). Null on every
+-- existing row, which rotation then marks as it does any other.
+ALTER TABLE "oauth_tokens" ADD COLUMN "rotated_at" timestamp;