@pristine-ts/common 2.0.5 → 2.0.7

package/dist/types/models/span-marker.model.d.ts

@@ -0,0 +1,36 @@
+/**
+ * A named, timestamped marker attached to a `Span`. Represents a noteworthy moment
+ * inside the span's lifetime that doesn't warrant a child span of its own — e.g.
+ * "validation passed", "rate limit check ok", "found 50 rows in DB".
+ *
+ * **Markers are instants, not durations.** They carry a single timestamp; they have no
+ * children and no end date. If you need hierarchical timing, spawn a child `Span`
+ * instead — that gives you start/end semantics and its own marker list.
+ *
+ * Modeled after OpenTelemetry's "span events" concept (we renamed `event` → `marker`
+ * here because `Event` is heavily overloaded in Pristine's dispatched-event domain —
+ * `Event<T>`, `EventHandler`, `EventPipeline`, `EventDispatcher`, etc.). A `Span` carries
+ * `markers: SpanMarker[]` alongside its `children: Span[]`. Renderers interleave markers
+ * with child spans by timestamp to produce a chronological trail of what happened.
+ *
+ * Use `TracingManager.addMarkerToCurrentSpan(message, attributes?)` to add one — it
+ * finds the most-recently-started in-progress span and attaches the marker there.
+ */
+export declare class SpanMarker {
+    readonly message: string;
+    /**
+     * The timestamp in milliseconds at which the marker was created. Used to interleave
+     * markers with sibling spans when rendering a sorted trail.
+     */
+    readonly timestamp: number;
+    /**
+     * Free-form attributes attached to the marker. String-keyed for cheap serialization,
+     * mirroring `Span.context`'s shape. `undefined` when the marker carries no metadata.
+     */
+    readonly attributes?: {
+        [key: string]: string;
+    };
+    constructor(message: string, attributes?: {
+        [key: string]: string;
+    });
+}

package/dist/types/models/span.model.d.ts

@@ -1,5 +1,5 @@
-import { SpanEvent } from "./span-event.model";
 import { SpanLifecycleOwnerInterface } from "./span-lifecycle-owner.interface";
+import { SpanMarker } from "./span-marker.model";
 import { Trace } from "./trace.model";
 /**
  * This model represents a span.
@@ -39,9 +39,12 @@ export declare class Span {
      * Named, timestamped markers attached to this span. Use these for noteworthy moments
      * inside the span's lifetime that don't warrant their own child span — e.g.
      * "validation passed", "found 50 rows in DB". Empty by default; populated by
-     * `TracingManager.addEventToCurrentSpan(...)`.
+     * `TracingManager.addMarkerToCurrentSpan(...)`.
+     *
+     * Markers are flat by design (instants, not durations). For hierarchical timing, use
+     * child spans.
      */
-    events: SpanEvent[];
+    markers: SpanMarker[];
     /**
      * The context associated with the span.
      */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pristine-ts/common",
-  "version": "2.0.5",
+  "version": "2.0.7",
   "description": "",
   "module": "dist/lib/esm/common.module.js",
   "main": "dist/lib/cjs/common.module.js",
@@ -63,5 +63,5 @@
       "src/*.{js,ts}"
     ]
   },
-  "gitHead": "9a960b330ee1961bb9a6151ce50257c4d8ccd48d"
+  "gitHead": "8788c711f72b7ebdcec76bc8f6a56d51af143087"
 }

package/dist/lib/cjs/models/span-event.model.js

@@ -1,28 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.SpanEvent = void 0;
-/**
- * A named, timestamped marker attached to a `Span`. Represents a noteworthy moment
- * inside the span's lifetime that doesn't warrant a child span of its own — e.g.
- * "validation passed", "rate limit check ok", "found 50 rows in DB".
- *
- * Modeled after OpenTelemetry's "span events" concept: a `Span` carries `events: SpanEvent[]`
- * alongside its `children: Span[]`. Renderers (the console/file tracer output, etc.) interleave
- * events with spans by timestamp to produce a chronological trail of what happened during the span.
- *
- * Use `TracingManager.addEventToCurrentSpan(message, attributes?)` to add one — it finds
- * the most-recently-started in-progress span and attaches the event there.
- */
-class SpanEvent {
-    constructor(message, attributes) {
-        this.message = message;
-        /**
-         * The timestamp in milliseconds at which the event was created. Used to interleave
-         * events with sibling spans when rendering a sorted trail.
-         */
-        this.timestamp = Date.now();
-        this.attributes = attributes;
-    }
-}
-exports.SpanEvent = SpanEvent;
-//# sourceMappingURL=span-event.model.js.map

package/dist/lib/cjs/models/span-event.model.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"span-event.model.js","sourceRoot":"","sources":["../../../../src/models/span-event.model.ts"],"names":[],"mappings":";;;AAAA;;;;;;;;;;;GAWG;AACH,MAAa,SAAS;IAapB,YAA4B,OAAe,EAAE,UAAsC;QAAvD,YAAO,GAAP,OAAO,CAAQ;QAZ3C;;;WAGG;QACa,cAAS,GAAW,IAAI,CAAC,GAAG,EAAE,CAAC;QAS7C,IAAI,CAAC,UAAU,GAAG,UAAU,CAAC;IAC/B,CAAC;CACF;AAhBD,8BAgBC"}

package/dist/lib/esm/models/span-event.model.js

@@ -1,24 +0,0 @@
-/**
- * A named, timestamped marker attached to a `Span`. Represents a noteworthy moment
- * inside the span's lifetime that doesn't warrant a child span of its own — e.g.
- * "validation passed", "rate limit check ok", "found 50 rows in DB".
- *
- * Modeled after OpenTelemetry's "span events" concept: a `Span` carries `events: SpanEvent[]`
- * alongside its `children: Span[]`. Renderers (the console/file tracer output, etc.) interleave
- * events with spans by timestamp to produce a chronological trail of what happened during the span.
- *
- * Use `TracingManager.addEventToCurrentSpan(message, attributes?)` to add one — it finds
- * the most-recently-started in-progress span and attaches the event there.
- */
-export class SpanEvent {
-    constructor(message, attributes) {
-        this.message = message;
-        /**
-         * The timestamp in milliseconds at which the event was created. Used to interleave
-         * events with sibling spans when rendering a sorted trail.
-         */
-        this.timestamp = Date.now();
-        this.attributes = attributes;
-    }
-}
-//# sourceMappingURL=span-event.model.js.map

package/dist/lib/esm/models/span-event.model.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"span-event.model.js","sourceRoot":"","sources":["../../../../src/models/span-event.model.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AACH,MAAM,OAAO,SAAS;IAapB,YAA4B,OAAe,EAAE,UAAsC;QAAvD,YAAO,GAAP,OAAO,CAAQ;QAZ3C;;;WAGG;QACa,cAAS,GAAW,IAAI,CAAC,GAAG,EAAE,CAAC;QAS7C,IAAI,CAAC,UAAU,GAAG,UAAU,CAAC;IAC/B,CAAC;CACF"}

package/dist/types/models/span-event.model.d.ts

@@ -1,30 +0,0 @@
-/**
- * A named, timestamped marker attached to a `Span`. Represents a noteworthy moment
- * inside the span's lifetime that doesn't warrant a child span of its own — e.g.
- * "validation passed", "rate limit check ok", "found 50 rows in DB".
- *
- * Modeled after OpenTelemetry's "span events" concept: a `Span` carries `events: SpanEvent[]`
- * alongside its `children: Span[]`. Renderers (the console/file tracer output, etc.) interleave
- * events with spans by timestamp to produce a chronological trail of what happened during the span.
- *
- * Use `TracingManager.addEventToCurrentSpan(message, attributes?)` to add one — it finds
- * the most-recently-started in-progress span and attaches the event there.
- */
-export declare class SpanEvent {
-    readonly message: string;
-    /**
-     * The timestamp in milliseconds at which the event was created. Used to interleave
-     * events with sibling spans when rendering a sorted trail.
-     */
-    readonly timestamp: number;
-    /**
-     * Free-form attributes attached to the event. String-keyed for cheap serialization,
-     * mirroring `Span.context`'s shape. `undefined` when the event carries no metadata.
-     */
-    readonly attributes?: {
-        [key: string]: string;
-    };
-    constructor(message: string, attributes?: {
-        [key: string]: string;
-    });
-}