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

package/dist/modules/write-access/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/modules/write-access/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AACH,OAAO,EAAE,cAAc,EAAE,cAAc,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC"}

package/dist/shared/listener-seam.d.ts

@@ -0,0 +1,34 @@
+import type { ILogger } from './logger.contract.js';
+/**
+ * A listener answers how it reached the people an event concerns — a
+ * non-empty channel name, `'email'` say — or null when it did not (nothing
+ * configured, nobody to tell, the send failed). It is awaited: the caller's
+ * answer says who was notified, truthfully, so a listener bounds its own
+ * wait. A throw is logged and counts as null; it never fails the caller. An
+ * empty name is no channel and counts as null too.
+ */
+export type NotifyingListener<E> = (event: E) => Promise<string | null>;
+/**
+ * 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 declare class ListenerSeam<E> {
+    private readonly log;
+    private readonly failed;
+    private readonly 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: ILogger, failed: string);
+    add(listener: NotifyingListener<E>): void;
+    /** Run every listener in registration order; the channels that reached somebody, in that order. */
+    run(event: E): Promise<string[]>;
+}
+//# sourceMappingURL=listener-seam.d.ts.map

package/dist/shared/listener-seam.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"listener-seam.d.ts","sourceRoot":"","sources":["../../src/shared/listener-seam.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,sBAAsB,CAAC;AAEpD;;;;;;;GAOG;AACH,MAAM,MAAM,iBAAiB,CAAC,CAAC,IAAI,CAAC,KAAK,EAAE,CAAC,KAAK,OAAO,CAAC,MAAM,GAAG,IAAI,CAAC,CAAC;AAExE;;;;;;;;GAQG;AACH,qBAAa,YAAY,CAAC,CAAC;IASvB,OAAO,CAAC,QAAQ,CAAC,GAAG;IACpB,OAAO,CAAC,QAAQ,CAAC,MAAM;IATzB,OAAO,CAAC,QAAQ,CAAC,SAAS,CAA8B;IAExD;;;;OAIG;gBAEgB,GAAG,EAAE,OAAO,EACZ,MAAM,EAAE,MAAM;IAGjC,GAAG,CAAC,QAAQ,EAAE,iBAAiB,CAAC,CAAC,CAAC,GAAG,IAAI;IAIzC,mGAAmG;IAC7F,GAAG,CAAC,KAAK,EAAE,CAAC,GAAG,OAAO,CAAC,MAAM,EAAE,CAAC;CAYvC"}

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;

package/migrations/0020_change_request_body_is_the_description.sql

@@ -0,0 +1,20 @@
+-- A change request's body is its description and nothing else.
+--
+-- Comments go: no screen ever rendered one, so a comment posted through the
+-- API or an agent tool was invisible to everyone. The routes, the service
+-- methods and the agent tools went with this release; the rows go here. A
+-- request's title and description are edited in place instead
+-- (`PATCH /api/workflow/change-requests/:number`, `update_change_request`).
+--
+-- An access request's level and note become columns of the request. Until
+-- now the body carried them in hidden markers (and an `## Affected owners`
+-- block nothing read back); the start that applies this moves what the old
+-- bodies held onto these columns and leaves the prose, once, in application
+-- code (`moveLegacyRequestBodies` in `migrate.ts`: the column is sealed, SQL
+-- cannot read it), recorded in `data_migrations` (0021) by the transaction
+-- that does it.
+ALTER TABLE "pr_comments" DISABLE ROW LEVEL SECURITY;--> statement-breakpoint
+DROP TABLE "pr_comments" CASCADE;--> statement-breakpoint
+ALTER TABLE "change_requests" ADD COLUMN "access_request_level" text;--> statement-breakpoint
+ALTER TABLE "change_requests" ADD COLUMN "access_request_note" text;--> statement-breakpoint
+ALTER TABLE "change_requests" ADD CONSTRAINT "change_requests_access_request_level_check" CHECK ("change_requests"."access_request_level" IS NULL OR "change_requests"."access_request_level" IN ('write', 'owner'));

package/migrations/0021_data_migrations_ledger.sql

@@ -0,0 +1,11 @@
+-- The ledger of the DATA halves of migrations: the rewrites SQL cannot do
+-- because they read sealed columns, run by the application right after the
+-- SQL history under the same lock. One row per pass, written in the SAME
+-- transaction as the rows it rewrote, so a pass is recorded done exactly when
+-- its work is; a start that crashed between drizzle's own ledger and the pass
+-- leaves no row, and the next start runs it. First used by 0020's body move.
+CREATE TABLE "data_migrations" (
+	"name" text PRIMARY KEY NOT NULL,
+	"applied_at" timestamp DEFAULT now() NOT NULL,
+	"note" text
+);