monday-cli 0.2.0

package/dist/api/dry-run.d.ts

@@ -0,0 +1,338 @@
+/**
+ * Dry-run engine (`cli-design.md` §6.4 + §5.3, `v0.1-plan.md` §3 M5a).
+ *
+ * Single export `planChanges` — given a board / item / set-pair list,
+ * runs every read-side resolution that the matching live mutation
+ * would run (column lookup, value translation, current-state read)
+ * and emits a `planned_changes[]` array byte-compatible with the
+ * `cli-design.md` §6.4 sample.
+ *
+ * **Why a separate module.** column-values.ts owns *translation*;
+ * resolution lives in columns.ts; current-state reads live in the
+ * item GraphQL queries spread across the command surface. The
+ * dry-run engine is the unique spot that orchestrates all three for
+ * a planned-but-unsent mutation. Keeping it in its own module means
+ * M5b's three command surfaces (`item set` / `item clear` /
+ * `item update`) each call `planChanges(...)` once when `--dry-run`
+ * is set, rather than reimplementing the orchestration in three
+ * places.
+ *
+ * **All-or-nothing semantics.** Any resolution failure — unknown
+ * column, ambiguous column, unsupported type, unknown email — fails
+ * the entire batch. cli-design §6.4 prescribes the dry-run envelope
+ * as a single `data: null` + populated `planned_changes` shape;
+ * surfacing partial plans would force the caller to second-guess
+ * which entries actually planned versus which silently dropped.
+ * The engine collects every `--set` pair before translating, but
+ * the first failing pair short-circuits — the typed error bubbles
+ * with whatever `details` the underlying resolver / translator
+ * built.
+ *
+ * **Mutation kind selection** (`change_simple_column_value` /
+ * `change_column_value` / `change_multiple_column_values`) goes
+ * through `selectMutation`, so the dry-run engine and the
+ * eventually-live M5b mutation pick the same wire shape from the
+ * same source of truth. The `operation` field in each
+ * `PlannedChange` reflects what the live call would issue.
+ *
+ * **Resolved-from echoes.** Two slots, one per kind:
+ *   - **Date** — relative tokens carry a `DateResolution`
+ *     (`{input, timezone, now}`) on the translated value. Rendered
+ *     as `details.resolved_from` on the diff cell.
+ *   - **People** — the people translator emits a
+ *     `PeopleResolution` (`{tokens: [{input, resolved_id}, ...]}`)
+ *     pairing each input token with its resolved Monday user ID.
+ *     Rendered as `details.resolved_from` on people diff cells.
+ *
+ * Other types (status / dropdown / text / long_text / numbers and
+ * non-relative dates) emit no `details` block — there's nothing to
+ * resolve beyond what's already visible in the wire payload.
+ */
+import type { MondayClient } from './client.js';
+import type { JsonValue } from '../types/json.js';
+import { type ResolverWarning } from './columns.js';
+import { type DateResolutionContext, type PeopleResolutionContext } from './column-values.js';
+import type { ParsedSetRawExpression } from './raw-write.js';
+/**
+ * One agent-supplied `--set <token>=<value>` pair, pre-split by the
+ * command layer into the resolution token and the raw value. The
+ * engine handles resolution + translation; argv splitting (per
+ * cli-design §5.3 step 3) belongs upstream.
+ */
+export interface SetEntry {
+    /** The raw column token agent typed (`status`, `due`, `id:status_4`). */
+    readonly token: string;
+    /** The raw value agent typed (post-`=` split). */
+    readonly value: string;
+}
+export interface PlanChangesInputs {
+    readonly client: MondayClient;
+    readonly boardId: string;
+    readonly itemId: string;
+    /** The full list of `--set` pairs the command layer parsed. */
+    readonly setEntries: readonly SetEntry[];
+    /**
+     * The list of `--set-raw` pairs the command layer parsed (M8
+     * escape-hatch surface). Each entry is the result of
+     * `parseSetRawExpression` from `api/raw-write.ts` — token + parsed
+     * `JsonObject` payload + the original `<json>` string. Resolution
+     * runs through the same `resolveColumnWithRefresh` path as
+     * `setEntries`; the post-resolution gate (`translateRawColumnValue`)
+     * applies the read-only-forever / files-shaped reject lists per
+     * cli-design §5.3 escape-hatch contract. The diff `to` side echoes
+     * the parsed JsonObject verbatim (whitespace + key ordering from
+     * the original argv string aren't preserved — equivalent payloads
+     * may render differently per cli-design §5.3 line 973-978).
+     */
+    readonly rawEntries?: readonly ParsedSetRawExpression[];
+    /**
+     * Optional rename — the new value for the item's `name` field.
+     * Plumbed through `monday item update --name <n>`. The engine
+     * treats `name` as a synthetic field (it isn't a column on Monday's
+     * board.columns surface) — column resolution is skipped for the
+     * `name` slot, and the dry-run diff carries an extra `name` key
+     * alongside any column diff entries. When passed alongside one or
+     * more `setEntries`, the operation rolls into
+     * `change_multiple_column_values` with `name` included in the
+     * `column_values` map per Monday's API. Alone, the operation is
+     * `change_simple_column_value(column_id: "name", value: <n>)`.
+     */
+    readonly nameChange?: string;
+    /**
+     * Date-resolution context — clock + tz for relative tokens. M5b's
+     * command layer plumbs `MONDAY_TIMEZONE` env override here. When
+     * omitted, the date translator falls back to system clock + tz.
+     */
+    readonly dateResolution?: DateResolutionContext;
+    /**
+     * People-resolution context — `resolveMe` + `resolveEmail`.
+     * Required when any `--set` pair targets a `people` column;
+     * `translateColumnValueAsync` raises `internal_error` if missing.
+     */
+    readonly peopleResolution?: PeopleResolutionContext;
+    /** Cache root + tz from process.env; defaults to `process.env`. */
+    readonly env?: NodeJS.ProcessEnv;
+    /** `--no-cache`: skip the column-metadata cache entirely. */
+    readonly noCache?: boolean;
+}
+/**
+ * One planned change — the §6.4 wire shape. The engine returns an
+ * array of these (length 1 in v0.1; M5b's bulk path produces N).
+ *
+ * Field order matches the sample at cli-design.md §6.4 lines
+ * 1206-1217 byte-for-byte: `operation`, `board_id`, `item_id`,
+ * `resolved_ids`, `diff`. Inserting a field reorders the JSON
+ * output — pinned by snapshot test against the literal sample.
+ */
+export interface PlannedChange {
+    /** The Monday mutation the live `--no-dry-run` call would issue. */
+    readonly operation: 'change_simple_column_value' | 'change_column_value' | 'change_multiple_column_values';
+    readonly board_id: string;
+    readonly item_id: string;
+    /**
+     * Token → resolved column ID map. Per §6.4: agents capture
+     * `resolved_ids[token]` for stable downstream calls — the human-
+     * friendly token in the original `--set` may be a column title
+     * that gets renamed; the resolved ID is permanent.
+     */
+    readonly resolved_ids: Readonly<Record<string, string>>;
+    /**
+     * Resolved-column-ID → diff cell. `from` is the parsed Monday
+     * value the column currently holds (or `null` for an empty cell);
+     * `to` is the wire payload the live mutation would send. The
+     * optional `details.resolved_from` carries the resolution echo
+     * for date-relative tokens and people inputs.
+     */
+    readonly diff: Readonly<Record<string, DiffCell>>;
+}
+/**
+ * One column's diff cell. `from` and `to` are JSON-shaped for the
+ * envelope; details (when present) carries the resolution echo for
+ * date / people inputs. cli-design §6.4 lines 1213-1214 pin the
+ * shape — `details` is an optional sibling of `from` / `to`,
+ * present only when the translator emitted an echo.
+ */
+export interface DiffCell {
+    readonly from: JsonValue;
+    readonly to: JsonValue;
+    readonly details?: {
+        readonly resolved_from: JsonValue;
+    };
+}
+export interface PlanChangesResult {
+    readonly plannedChanges: readonly PlannedChange[];
+    /**
+     * Aggregate envelope source: `live` if any leg fetched live (the
+     * item read always does); `cache` only if every leg hit cache;
+     * `mixed` when the column-resolution refresh path fired. v0.1's
+     * dry-run always reads the item live — there's no item-state
+     * cache — so `source` is always `live` or `mixed` in practice.
+     * The `cache` value is reserved for v0.2 when item-state caching
+     * lands.
+     */
+    readonly source: 'live' | 'cache' | 'mixed';
+    readonly cacheAgeSeconds: number | null;
+    readonly warnings: readonly ResolverWarning[];
+}
+/**
+ * Resolves every `--set` pair, fetches the item's current state,
+ * translates each value, and assembles a single `PlannedChange`
+ * (v0.1 — one item per call). All-or-nothing: any resolution
+ * failure throws the typed error directly so the command layer
+ * surfaces it through the runner's normal error path.
+ */
+export declare const planChanges: (inputs: PlanChangesInputs) => Promise<PlanChangesResult>;
+export interface PlanClearInputs {
+    readonly client: MondayClient;
+    readonly boardId: string;
+    readonly itemId: string;
+    /** The single column token the agent typed (`status`, `id:status_4`). */
+    readonly token: string;
+    /** Cache root + tz from process.env; defaults to `process.env`. */
+    readonly env?: NodeJS.ProcessEnv;
+    /** `--no-cache`: skip the column-metadata cache entirely. */
+    readonly noCache?: boolean;
+}
+/**
+ * Single-column clear-mode dry-run. cli-design §4.3 ships `item clear`
+ * as a single-column-only verb (no `--where` bulk path; that's
+ * `item update`'s territory), so the engine doesn't need a
+ * setEntries-style multi-token shape — one token in, one
+ * `PlannedChange` out. Reuses the same column-resolution +
+ * archived-detection + item-state-read machinery as `planChanges`,
+ * routed through `translateColumnClear` for the per-type clear
+ * payload.
+ *
+ * **`from` / `to` shape.** Same `DiffCell` contract as
+ * `planChanges` — the `from` side decodes the current Monday cell
+ * value (or `null` for empty cells); the `to` side is the wire
+ * payload the live mutation would send (`""` for simple types, `{}`
+ * for rich types). cli-design §6.4's diff-cell shape is invariant
+ * across set / clear.
+ */
+export declare const planClear: (inputs: PlanClearInputs) => Promise<PlanChangesResult>;
+/**
+ * Discriminator over the two M9 create shapes (cli-design §6.4
+ * "Item-create shape").
+ *
+ *   - `item` — top-level `create_item`. Resolves columns against
+ *     `boardId`. `groupId` / `position` ride into the planned shape's
+ *     hoisted slots (`group_id`, `position`).
+ *   - `subitem` — `create_subitem`. Resolves columns against
+ *     `subitemsBoardId` (the auto-generated subitems board the
+ *     command layer derived from the parent's `subtasks` column,
+ *     classic-board-only). The planned shape omits `board_id` and
+ *     hoists `parent_item_id` instead. `--group` / `--position` are
+ *     argv-rejected before reaching here.
+ *
+ * The hierarchy_type gate (`multi_level` rejection) and the
+ * `--relative-to` same-board verification both live in the command
+ * layer — `planCreate` runs after those checks pass.
+ */
+export type CreateMode = {
+    readonly kind: 'item';
+    readonly boardId: string;
+    readonly groupId?: string;
+    readonly position?: {
+        readonly method: 'before' | 'after';
+        readonly relativeTo: string;
+    };
+} | {
+    readonly kind: 'subitem';
+    readonly parentItemId: string;
+    /**
+     * The subitems-board ID the column resolver targets. The
+     * command layer derives this from the parent's `subtasks`
+     * column's `settings_str.boardIds[0]` (classic-only); when
+     * that derivation isn't possible (e.g. parent's board has no
+     * `subtasks` column yet, or the settings_str is empty), the
+     * command rejects with `usage_error` before reaching
+     * planCreate.
+     */
+    readonly subitemsBoardId: string;
+};
+export interface PlanCreateInputs {
+    readonly client: MondayClient;
+    readonly mode: CreateMode;
+    /** The new item's name (validated as non-empty by the command layer). */
+    readonly name: string;
+    readonly setEntries: readonly SetEntry[];
+    readonly rawEntries?: readonly ParsedSetRawExpression[];
+    readonly dateResolution?: DateResolutionContext;
+    readonly peopleResolution?: PeopleResolutionContext;
+    readonly env?: NodeJS.ProcessEnv;
+    readonly noCache?: boolean;
+}
+/**
+ * One planned create — cli-design §6.4 "Item-create shape" /
+ * "Subitem variant". The shape is intentionally distinct from the
+ * column-mutation `PlannedChange`:
+ *
+ *   - `operation` discriminates `'create_item' | 'create_subitem'`.
+ *   - `name`, `group_id`, `position`, `parent_item_id` are
+ *     **hoisted** (top-level slots) rather than buried inside `diff`,
+ *     mirroring the comment-create shape's preference for agent-
+ *     scannable fields.
+ *   - `diff[<col>].from` is always `null` (the item doesn't exist
+ *     yet; nothing to diff against).
+ *
+ * Optional slots appear only when their input was supplied:
+ *   - `group_id` — only when the agent passed `--group <gid>`
+ *     (omitted = Monday assigns the default group server-side).
+ *   - `position` — only when both `--position` and `--relative-to`
+ *     were supplied. Subitem variant always omits.
+ *   - `board_id` — present on `create_item` only; the subitem
+ *     variant omits it (the subitems board is derived server-side
+ *     from the parent and surfacing it as `board_id` would falsely
+ *     imply the agent's `--board` value).
+ */
+export interface CreatePlannedChange {
+    readonly operation: 'create_item' | 'create_subitem';
+    readonly board_id?: string;
+    readonly name: string;
+    readonly group_id?: string;
+    readonly position?: {
+        readonly method: 'before' | 'after';
+        readonly relative_to: string;
+    };
+    readonly parent_item_id?: string;
+    readonly resolved_ids: Readonly<Record<string, string>>;
+    readonly diff: Readonly<Record<string, DiffCell>>;
+}
+export interface PlanCreateResult {
+    readonly plannedChanges: readonly CreatePlannedChange[];
+    /**
+     * Aggregate envelope source: same merge rule as `planChanges`
+     * (`live` / `cache` / `mixed`). When `setEntries` and `rawEntries`
+     * are both empty, no resolution legs run and `source` is `'none'` —
+     * dry-run create with no `--set` flags fires no API calls at all.
+     */
+    readonly source: 'live' | 'cache' | 'mixed' | 'none';
+    readonly cacheAgeSeconds: number | null;
+    readonly warnings: readonly ResolverWarning[];
+}
+/**
+ * Resolves every `--set` / `--set-raw` token, translates each value,
+ * and assembles a single `CreatePlannedChange`. **No item-state read**
+ * — the item doesn't exist yet, so every diff cell's `from` is `null`.
+ *
+ * **All-or-nothing semantics** (same as `planChanges`). Any resolution
+ * failure (`column_not_found` / `ambiguous_column` / `column_archived`
+ * / `unsupported_column_type` / `user_not_found` / duplicate token /
+ * duplicate resolved id) aborts before any further work.
+ *
+ * **Diff `to` projection.** The wire shape every Monday create
+ * mutation accepts is `column_values: JSON!` — the same map shape
+ * `change_multiple_column_values` accepts. So the diff `to` side
+ * routes through `bundleColumnValues` for byte-equivalence with the
+ * live mutation's wire payload, including the `long_text` re-wrap
+ * (`{text: <value>}` inside the map).
+ *
+ * **No-`--set` path.** Create with neither `--set` nor `--set-raw`
+ * is valid (Monday accepts `create_item(item_name: ..., column_values:
+ * null)`). The function short-circuits the resolution loop and
+ * returns a `CreatePlannedChange` with empty `resolved_ids` and `diff`.
+ * `source: 'none'` because no API call fired.
+ */
+export declare const planCreate: (inputs: PlanCreateInputs) => Promise<PlanCreateResult>;
+//# sourceMappingURL=dry-run.d.ts.map

package/dist/api/dry-run.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"dry-run.d.ts","sourceRoot":"","sources":["../../src/api/dry-run.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiDG;AAGH,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,aAAa,CAAC;AAChD,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,kBAAkB,CAAC;AAClD,OAAO,EAEL,KAAK,eAAe,EACrB,MAAM,cAAc,CAAC;AAWtB,OAAO,EAIL,KAAK,qBAAqB,EAE1B,KAAK,uBAAuB,EAG7B,MAAM,oBAAoB,CAAC;AAC5B,OAAO,KAAK,EAAE,sBAAsB,EAAE,MAAM,gBAAgB,CAAC;AAQ7D;;;;;GAKG;AACH,MAAM,WAAW,QAAQ;IACvB,yEAAyE;IACzE,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,kDAAkD;IAClD,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;CACxB;AAED,MAAM,WAAW,iBAAiB;IAChC,QAAQ,CAAC,MAAM,EAAE,YAAY,CAAC;IAC9B,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;IACxB,+DAA+D;IAC/D,QAAQ,CAAC,UAAU,EAAE,SAAS,QAAQ,EAAE,CAAC;IACzC;;;;;;;;;;;;OAYG;IACH,QAAQ,CAAC,UAAU,CAAC,EAAE,SAAS,sBAAsB,EAAE,CAAC;IACxD;;;;;;;;;;;OAWG;IACH,QAAQ,CAAC,UAAU,CAAC,EAAE,MAAM,CAAC;IAC7B;;;;OAIG;IACH,QAAQ,CAAC,cAAc,CAAC,EAAE,qBAAqB,CAAC;IAChD;;;;OAIG;IACH,QAAQ,CAAC,gBAAgB,CAAC,EAAE,uBAAuB,CAAC;IACpD,mEAAmE;IACnE,QAAQ,CAAC,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,CAAC;IACjC,6DAA6D;IAC7D,QAAQ,CAAC,OAAO,CAAC,EAAE,OAAO,CAAC;CAC5B;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,aAAa;IAC5B,oEAAoE;IACpE,QAAQ,CAAC,SAAS,EACd,4BAA4B,GAC5B,qBAAqB,GACrB,+BAA+B,CAAC;IACpC,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB;;;;;OAKG;IACH,QAAQ,CAAC,YAAY,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;IACxD;;;;;;OAMG;IACH,QAAQ,CAAC,IAAI,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC,CAAC;CACnD;AAED;;;;;;GAMG;AACH,MAAM,WAAW,QAAQ;IACvB,QAAQ,CAAC,IAAI,EAAE,SAAS,CAAC;IACzB,QAAQ,CAAC,EAAE,EAAE,SAAS,CAAC;IACvB,QAAQ,CAAC,OAAO,CAAC,EAAE;QAAE,QAAQ,CAAC,aAAa,EAAE,SAAS,CAAA;KAAE,CAAC;CAC1D;AAED,MAAM,WAAW,iBAAiB;IAChC,QAAQ,CAAC,cAAc,EAAE,SAAS,aAAa,EAAE,CAAC;IAClD;;;;;;;;OAQG;IACH,QAAQ,CAAC,MAAM,EAAE,MAAM,GAAG,OAAO,GAAG,OAAO,CAAC;IAC5C,QAAQ,CAAC,eAAe,EAAE,MAAM,GAAG,IAAI,CAAC;IACxC,QAAQ,CAAC,QAAQ,EAAE,SAAS,eAAe,EAAE,CAAC;CAC/C;AAED;;;;;;GAMG;AACH,eAAO,MAAM,WAAW,GACtB,QAAQ,iBAAiB,KACxB,OAAO,CAAC,iBAAiB,CA0I3B,CAAC;AAsCF,MAAM,WAAW,eAAe;IAC9B,QAAQ,CAAC,MAAM,EAAE,YAAY,CAAC;IAC9B,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;IACxB,yEAAyE;IACzE,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,mEAAmE;IACnE,QAAQ,CAAC,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,CAAC;IACjC,6DAA6D;IAC7D,QAAQ,CAAC,OAAO,CAAC,EAAE,OAAO,CAAC;CAC5B;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,eAAO,MAAM,SAAS,GACpB,QAAQ,eAAe,KACtB,OAAO,CAAC,iBAAiB,CA+E3B,CAAC;AAMF;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,MAAM,UAAU,GAClB;IACE,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,OAAO,CAAC,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,QAAQ,CAAC,EAAE;QAClB,QAAQ,CAAC,MAAM,EAAE,QAAQ,GAAG,OAAO,CAAC;QACpC,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;KAC7B,CAAC;CACH,GACD;IACE,QAAQ,CAAC,IAAI,EAAE,SAAS,CAAC;IACzB,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;IAC9B;;;;;;;;OAQG;IACH,QAAQ,CAAC,eAAe,EAAE,MAAM,CAAC;CAClC,CAAC;AAEN,MAAM,WAAW,gBAAgB;IAC/B,QAAQ,CAAC,MAAM,EAAE,YAAY,CAAC;IAC9B,QAAQ,CAAC,IAAI,EAAE,UAAU,CAAC;IAC1B,yEAAyE;IACzE,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,UAAU,EAAE,SAAS,QAAQ,EAAE,CAAC;IACzC,QAAQ,CAAC,UAAU,CAAC,EAAE,SAAS,sBAAsB,EAAE,CAAC;IACxD,QAAQ,CAAC,cAAc,CAAC,EAAE,qBAAqB,CAAC;IAChD,QAAQ,CAAC,gBAAgB,CAAC,EAAE,uBAAuB,CAAC;IACpD,QAAQ,CAAC,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,CAAC;IACjC,QAAQ,CAAC,OAAO,CAAC,EAAE,OAAO,CAAC;CAC5B;AAED;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,WAAW,mBAAmB;IAClC,QAAQ,CAAC,SAAS,EAAE,aAAa,GAAG,gBAAgB,CAAC;IACrD,QAAQ,CAAC,QAAQ,CAAC,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,QAAQ,CAAC,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,QAAQ,CAAC,EAAE;QAClB,QAAQ,CAAC,MAAM,EAAE,QAAQ,GAAG,OAAO,CAAC;QACpC,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;KAC9B,CAAC;IACF,QAAQ,CAAC,cAAc,CAAC,EAAE,MAAM,CAAC;IACjC,QAAQ,CAAC,YAAY,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;IACxD,QAAQ,CAAC,IAAI,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC,CAAC;CACnD;AAED,MAAM,WAAW,gBAAgB;IAC/B,QAAQ,CAAC,cAAc,EAAE,SAAS,mBAAmB,EAAE,CAAC;IACxD;;;;;OAKG;IACH,QAAQ,CAAC,MAAM,EAAE,MAAM,GAAG,OAAO,GAAG,OAAO,GAAG,MAAM,CAAC;IACrD,QAAQ,CAAC,eAAe,EAAE,MAAM,GAAG,IAAI,CAAC;IACxC,QAAQ,CAAC,QAAQ,EAAE,SAAS,eAAe,EAAE,CAAC;CAC/C;AAED;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,eAAO,MAAM,UAAU,GACrB,QAAQ,gBAAgB,KACvB,OAAO,CAAC,gBAAgB,CAgE1B,CAAC"}