@dudousxd/nestjs-catalog 0.17.0 → 0.19.0

package/dist/catalog.events.d.ts

@@ -14,7 +14,7 @@
  */
 export declare const CATALOG_LIB = "catalog";
 /** Every event name this package emits. Exported so a watcher can claim them. */
-export declare const CATALOG_EVENTS: readonly ["schema.changed", "snapshot.written", "snapshot.committed", "snapshot.dropped", "type.curated", "overlay.reset", "connector.run.started", "connector.run.finished", "transform.changed", "workflow.changed", "query.shared", "dashboard.shared"];
+export declare const CATALOG_EVENTS: readonly ["schema.changed", "snapshot.written", "snapshot.committed", "snapshot.dropped", "type.curated", "overlay.reset", "connector.run.started", "connector.run.finished", "transform.changed", "reusable-node.changed", "workflow.changed", "query.shared", "dashboard.shared"];
 export type CatalogEvent = (typeof CATALOG_EVENTS)[number];
 /**
  * Where each event sits in the life of one load.
@@ -286,6 +286,31 @@ export interface CatalogEventPayloads {
         version: number;
         changedBy: string;
     };
+    /**
+     * Someone changed a node body that several graphs share.
+     *
+     * The third authoring event, and the one that answers a question the other two
+     * cannot. `transform.changed` and `workflow.changed` both name something
+     * inside the graph that changed behaviour; this names a change **outside**
+     * every graph it affects. A load that started reading a different query last
+     * Tuesday, whose own graph has not been touched in a month, has its whole
+     * explanation here and nowhere else — which is precisely the silence that
+     * makes shared nodes dangerous and precisely what this event is for.
+     *
+     * It carries no list of the graphs downstream, deliberately. That list is a
+     * query (`GET reusable-nodes/:id/workflows`) and it is answered as of *now*,
+     * whereas an event is a record of one moment; freezing a list into the trail
+     * would produce a fact that is wrong by the following week and looks
+     * authoritative.
+     */
+    'reusable-node.changed': {
+        reusableNodeId: string;
+        name: string;
+        /** `source` or `sink` — see `REUSABLE_NODE_KINDS`. */
+        kind: string;
+        version: number;
+        changedBy: string;
+    };
     /**
      * Someone changed the wiring rather than the code.
      *

package/dist/catalog.events.js

@@ -32,6 +32,7 @@ exports.CATALOG_EVENTS = [
     'connector.run.started',
     'connector.run.finished',
     'transform.changed',
+    'reusable-node.changed',
     'workflow.changed',
     'query.shared',
     'dashboard.shared',
@@ -63,6 +64,13 @@ exports.CATALOG_EVENT_PHASE = {
     // one an earlier rank than the other would assert a causal order between two
     // edits that have none.
     'workflow.changed': 1,
+    // And the same rank again, for the same argument one step further out.
+    // Editing a reusable node is an authoring act that precedes the run being
+    // investigated, exactly as editing a transform or rewiring a graph is — and
+    // it is the one of the three that can change a load nobody edited, so a trace
+    // that could not place it beside the others would be missing the entry that
+    // explains the surprise.
+    'reusable-node.changed': 1,
     // Curation carries no snapshot id, so it never lands inside a trace and this
     // rank is never consulted. It is written out rather than left to the fallback
     // because the type demands every event have one, and a `Record` that has to