@declarion/react 0.43.0 → 0.45.0

package/dist-lib/lib/anchor.d.ts

@@ -0,0 +1,37 @@
+/**
+ * The anchor expression, TypeScript side.
+ *
+ * One grammar for "a moment relative to now", shared with the server
+ * (golang/internal/engine/anchor.go + duration.go). The language boundary is
+ * the only reason there are two implementations; nothing else may declare a
+ * third.
+ *
+ *   now            the current instant
+ *   now+3w         three weeks ahead
+ *   now-1d         one day back
+ *   now+3w-1d      the offsets compose, left to right
+ *
+ * Units are Go's plus `d` (24h) and `w` (7d). Calendar units `y` and `mo` are
+ * refused: they have no fixed length, so `1mo` from the 31st has no answer this
+ * platform is willing to invent.
+ */
+/**
+ * One magnitude, and the running total of an anchor's offsets, may not exceed
+ * 100 years. Beyond that the server's arithmetic saturates and `now+N` and
+ * `now-N` collapse to the same instant - a predicate written to match nothing
+ * matching everything. The client refuses the same inputs so a template that
+ * would fail on the server does not silently produce a different moment here.
+ */
+export declare const MAX_DURATION_MAGNITUDE_MS: number;
+/** At most this many signed offsets in one anchor expression. */
+export declare const MAX_ANCHOR_OFFSETS = 8;
+/** Parse one unsigned magnitude (`3w`, `1h30m`). Returns null when invalid. */
+export declare function parseDurationMagnitudeMs(text: string): number | null;
+/**
+ * Parse an anchor expression WITHOUT any surface wrapper - `now`, `now+3w`,
+ * `now+3w-1d` - and return the summed offset in milliseconds. Returns null when
+ * the text is not a valid anchor expression, which the caller surfaces the way
+ * it surfaces any unresolved token: by leaving the template visible rather than
+ * writing a wrong moment.
+ */
+export declare function parseAnchorOffsetMs(expr: string): number | null;