@geekmidas/constructs 10.0.0-alpha.6 → 10.0.0-alpha.61

package/dist/Topic-CkxOTrMv.cjs

@@ -0,0 +1,104 @@
+const require_Construct = require("./Construct-DmvXceVY.cjs");
+let _geekmidas_manifest = require("@geekmidas/manifest");
+let _geekmidas_logger_console = require("@geekmidas/logger/console");
+let _geekmidas_events = require("@geekmidas/events");
+//#region src/topic/Topic.ts
+/**
+* A topic — pub/sub fan-out. Unlike a `Queue` (point-to-point, one consumer), a
+* topic is a *resource* owned by no single handler: it declares the event
+* contract, and any number of subscribers (`worker.topic(topic)`) bind to it.
+* `gkm build` discovers it into the manifest's `topics` field; infra provisions
+* an SNS topic.
+*
+* A construct publishes with `.event(topic, { type, payload })`, repeatable
+* across topics, each event going through its own topic's publisher. That also
+* puts `services.<topic>` in the handler, as `.dependsOn([topic])` does, for an
+* event the handler decides on itself.
+*
+* ```ts
+* export const users = new Topic('Users', {
+*   events: { 'user.created': z.object({ userId: z.string() }) },
+* });
+* ```
+*/
+var Topic = class extends require_Construct.Construct {
+	__IS_TOPIC__ = true;
+	static isTopic(obj) {
+		return Boolean(obj && obj.__IS_TOPIC__ === true && obj.type === "dev.geekmidas.resource.topic");
+	}
+	/**
+	* The canonical id this topic is declared under.
+	*
+	* Derived from the name, so `users` and `Users` are one topic. The name is
+	* left alone: subscribers bind to it and it is what the broker routes on.
+	*/
+	id;
+	/** The name it was declared with — what the broker routes on. */
+	name;
+	/**
+	* The event contract — a map of event type → payload schema. Named
+	* `eventSchemas` (not `events`) to avoid clashing with `Construct.events`,
+	* which is the array of `MappedEvent`s a construct *publishes*.
+	*/
+	eventSchemas;
+	/**
+	* The topic as a dependency — what `.dependsOn([users])` and
+	* `.event(users, …)` dissolve into, reachable as `services.users`.
+	*
+	* The producer, because publishing is the only thing depending on a topic
+	* can mean: a subscriber binds to the topic instead, and is never handed
+	* this. It reads `<NAME>_PUBLISHER_CONNECTION_STRING` and picks the
+	* transport from its protocol — `pgboss://` locally, `sns://` deployed.
+	*
+	* A field assigned once, not a getter: services are cached by object
+	* identity, and a fresh literal on every access never hit that cache.
+	*/
+	service;
+	/** The producer's env key, read by both {@link declare} and the service. */
+	connectionKey;
+	constructor(name, options) {
+		super("dev.geekmidas.resource.topic", _geekmidas_logger_console.DEFAULT_LOGGER, [], []);
+		this.name = name;
+		this.id = (0, _geekmidas_manifest.canonicalId)(name);
+		this.eventSchemas = options.events;
+		this.connectionKey = (0, _geekmidas_manifest.provideKey)(this.id, "publisherConnectionString");
+		const envVar = this.connectionKey;
+		const topic = this.name;
+		this.service = {
+			serviceName: (0, _geekmidas_manifest.serviceKey)(this.id),
+			async register({ envParser }) {
+				const { connectionString } = envParser.create((get) => ({ connectionString: get(envVar).string() })).parse();
+				return _geekmidas_events.Publisher.fromConnectionString(connectionString, { topic });
+			}
+		};
+	}
+	/**
+	* What this topic is in the manifest.
+	*
+	* Only the producer's key: a subscriber is *bound* to a topic rather than
+	* depending on it, so the binding is an edge the deploy target reads and not
+	* an env key anyone can hold. Locally both sides meet on the same broker.
+	*/
+	declare() {
+		return [{
+			kind: "topic",
+			id: this.id,
+			provides: [this.connectionKey],
+			events: this.eventTypes,
+			subscribers: []
+		}];
+	}
+	/** The event type names this topic carries. */
+	get eventTypes() {
+		return Object.keys(this.eventSchemas);
+	}
+};
+//#endregion
+Object.defineProperty(exports, "Topic", {
+	enumerable: true,
+	get: function() {
+		return Topic;
+	}
+});
+
+//# sourceMappingURL=Topic-CkxOTrMv.cjs.map

package/dist/Topic-CkxOTrMv.cjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"Topic-CkxOTrMv.cjs","names":["Construct","DEFAULT_LOGGER","canonicalId","provideKey","serviceKey","Publisher"],"sources":["../src/topic/Topic.ts"],"sourcesContent":["import {\n\ttype EventPublisher,\n\ttype EventPublisherConnectionString,\n\ttype PublishableMessage,\n\tPublisher,\n} from '@geekmidas/events';\nimport { DEFAULT_LOGGER } from '@geekmidas/logger/console';\nimport {\n\ttype ConstructName,\n\tcanonicalId,\n\ttype Declaration,\n\tprovideKey,\n\tserviceKey,\n} from '@geekmidas/manifest';\nimport type { InferStandardSchema } from '@geekmidas/schema';\nimport type { Service } from '@geekmidas/services';\nimport type { StandardSchemaV1 } from '@standard-schema/spec';\nimport { Construct, ConstructType } from '../Construct';\n\n/** A topic's event contract — a map of event type → payload schema. */\nexport type TopicEvents = Record<string, StandardSchemaV1>;\n\n/**\n * The union of wire messages a topic carries, derived from its event map:\n * `{ type: 'user.created'; payload: … } | { type: 'user.updated'; payload: … }`.\n */\nexport type TopicMessage<TEvents extends TopicEvents> = {\n\t[K in keyof TEvents & string]: PublishableMessage<\n\t\tK,\n\t\tInferStandardSchema<TEvents[K]>\n\t>;\n}[keyof TEvents & string];\n\n/**\n * A topic — pub/sub fan-out. Unlike a `Queue` (point-to-point, one consumer), a\n * topic is a *resource* owned by no single handler: it declares the event\n * contract, and any number of subscribers (`worker.topic(topic)`) bind to it.\n * `gkm build` discovers it into the manifest's `topics` field; infra provisions\n * an SNS topic.\n *\n * A construct publishes with `.event(topic, { type, payload })`, repeatable\n * across topics, each event going through its own topic's publisher. That also\n * puts `services.<topic>` in the handler, as `.dependsOn([topic])` does, for an\n * event the handler decides on itself.\n *\n * ```ts\n * export const users = new Topic('Users', {\n *   events: { 'user.created': z.object({ userId: z.string() }) },\n * });\n * ```\n */\nexport class Topic<\n\tTName extends string = string,\n\tTEvents extends TopicEvents = TopicEvents,\n> extends Construct {\n\t__IS_TOPIC__ = true;\n\n\tstatic isTopic(obj: unknown): obj is Topic<string, TopicEvents> {\n\t\treturn Boolean(\n\t\t\tobj &&\n\t\t\t\t(obj as { __IS_TOPIC__?: boolean }).__IS_TOPIC__ === true &&\n\t\t\t\t(obj as Construct).type === ConstructType.Topic,\n\t\t);\n\t}\n\n\t/**\n\t * The canonical id this topic is declared under.\n\t *\n\t * Derived from the name, so `users` and `Users` are one topic. The name is\n\t * left alone: subscribers bind to it and it is what the broker routes on.\n\t */\n\treadonly id: string;\n\n\t/** The name it was declared with — what the broker routes on. */\n\treadonly name: TName;\n\n\t/**\n\t * The event contract — a map of event type → payload schema. Named\n\t * `eventSchemas` (not `events`) to avoid clashing with `Construct.events`,\n\t * which is the array of `MappedEvent`s a construct *publishes*.\n\t */\n\treadonly eventSchemas: TEvents;\n\n\t/**\n\t * The topic as a dependency — what `.dependsOn([users])` and\n\t * `.event(users, …)` dissolve into, reachable as `services.users`.\n\t *\n\t * The producer, because publishing is the only thing depending on a topic\n\t * can mean: a subscriber binds to the topic instead, and is never handed\n\t * this. It reads `<NAME>_PUBLISHER_CONNECTION_STRING` and picks the\n\t * transport from its protocol — `pgboss://` locally, `sns://` deployed.\n\t *\n\t * A field assigned once, not a getter: services are cached by object\n\t * identity, and a fresh literal on every access never hit that cache.\n\t */\n\treadonly service: Service<\n\t\tUncapitalize<TName>,\n\t\tEventPublisher<TopicMessage<TEvents>>\n\t>;\n\n\t/** The producer's env key, read by both {@link declare} and the service. */\n\tprivate readonly connectionKey: string;\n\n\tconstructor(name: ConstructName<TName>, options: TopicOptions<TEvents>) {\n\t\tsuper(ConstructType.Topic, DEFAULT_LOGGER, [], []);\n\n\t\tthis.name = name as TName;\n\t\tthis.id = canonicalId(name as string);\n\t\tthis.eventSchemas = options.events;\n\t\tthis.connectionKey = provideKey(this.id, 'publisherConnectionString');\n\n\t\tconst envVar = this.connectionKey;\n\t\tconst topic = this.name as string;\n\t\tthis.service = {\n\t\t\tserviceName: serviceKey(this.id) as Uncapitalize<TName>,\n\t\t\tasync register({ envParser }) {\n\t\t\t\tconst { connectionString } = envParser\n\t\t\t\t\t.create((get) => ({ connectionString: get(envVar).string() }))\n\t\t\t\t\t.parse();\n\n\t\t\t\t// Named as a topic, so a broker with one address for everything\n\t\t\t\t// (pg-boss) fans each message out to every subscriber.\n\t\t\t\treturn Publisher.fromConnectionString<TopicMessage<TEvents>>(\n\t\t\t\t\tconnectionString as EventPublisherConnectionString,\n\t\t\t\t\t{ topic },\n\t\t\t\t);\n\t\t\t},\n\t\t};\n\t}\n\n\t/**\n\t * What this topic is in the manifest.\n\t *\n\t * Only the producer's key: a subscriber is *bound* to a topic rather than\n\t * depending on it, so the binding is an edge the deploy target reads and not\n\t * an env key anyone can hold. Locally both sides meet on the same broker.\n\t */\n\tdeclare(): Declaration[] {\n\t\treturn [\n\t\t\t{\n\t\t\t\tkind: 'topic',\n\t\t\t\tid: this.id,\n\t\t\t\tprovides: [this.connectionKey],\n\t\t\t\t// The contract this topic carries. Structural: which events exist\n\t\t\t\t// is a fact about the application, and a subscriber binding to one\n\t\t\t\t// that does not is a mistake worth catching at build.\n\t\t\t\tevents: this.eventTypes,\n\t\t\t\t// Bound rather than declared here — a subscriber names the topic,\n\t\t\t\t// not the other way round — so the build fills these from what it\n\t\t\t\t// found. Nested when it does, because position is the trigger.\n\t\t\t\tsubscribers: [],\n\t\t\t},\n\t\t];\n\t}\n\n\t/** The event type names this topic carries. */\n\tget eventTypes(): (keyof TEvents & string)[] {\n\t\treturn Object.keys(this.eventSchemas) as (keyof TEvents & string)[];\n\t}\n}\n\nexport interface TopicOptions<TEvents extends TopicEvents> {\n\t/** Each event this topic carries — its type, and its payload's schema. */\n\tevents: TEvents;\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;AAmDA,IAAa,QAAb,cAGUA,kBAAAA,UAAU;CACnB,eAAe;CAEf,OAAO,QAAQ,KAAiD;EAC/D,OAAO,QACN,OACE,IAAmC,iBAAiB,QACpD,IAAkB,SAAA,8BACrB;CACD;;;;;;;CAQA;;CAGA;;;;;;CAOA;;;;;;;;;;;;;CAcA;;CAMA;CAEA,YAAY,MAA4B,SAAgC;EACvE,MAAA,gCAA2BC,0BAAAA,gBAAgB,CAAC,GAAG,CAAC,CAAC;EAEjD,KAAK,OAAO;EACZ,KAAK,MAAA,GAAKC,oBAAAA,YAAAA,CAAY,IAAc;EACpC,KAAK,eAAe,QAAQ;EAC5B,KAAK,iBAAA,GAAgBC,oBAAAA,WAAAA,CAAW,KAAK,IAAI,2BAA2B;EAEpE,MAAM,SAAS,KAAK;EACpB,MAAM,QAAQ,KAAK;EACnB,KAAK,UAAU;GACd,cAAA,GAAaC,oBAAAA,WAAAA,CAAW,KAAK,EAAE;GAC/B,MAAM,SAAS,EAAE,aAAa;IAC7B,MAAM,EAAE,qBAAqB,UAC3B,QAAQ,SAAS,EAAE,kBAAkB,IAAI,MAAM,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,CAC7D,MAAM;IAIR,OAAOC,kBAAAA,UAAU,qBAChB,kBACA,EAAE,MAAM,CACT;GACD;EACD;CACD;;;;;;;;CASA,UAAyB;EACxB,OAAO,CACN;GACC,MAAM;GACN,IAAI,KAAK;GACT,UAAU,CAAC,KAAK,aAAa;GAI7B,QAAQ,KAAK;GAIb,aAAa,CAAC;EACf,CACD;CACD;;CAGA,IAAI,aAAyC;EAC5C,OAAO,OAAO,KAAK,KAAK,YAAY;CACrC;AACD"}

package/dist/Topic-hPffOsot.mjs

@@ -0,0 +1,99 @@
+import { t as Construct } from "./Construct-BO1X-kt9.mjs";
+import { canonicalId, provideKey, serviceKey } from "@geekmidas/manifest";
+import { DEFAULT_LOGGER } from "@geekmidas/logger/console";
+import { Publisher } from "@geekmidas/events";
+//#region src/topic/Topic.ts
+/**
+* A topic — pub/sub fan-out. Unlike a `Queue` (point-to-point, one consumer), a
+* topic is a *resource* owned by no single handler: it declares the event
+* contract, and any number of subscribers (`worker.topic(topic)`) bind to it.
+* `gkm build` discovers it into the manifest's `topics` field; infra provisions
+* an SNS topic.
+*
+* A construct publishes with `.event(topic, { type, payload })`, repeatable
+* across topics, each event going through its own topic's publisher. That also
+* puts `services.<topic>` in the handler, as `.dependsOn([topic])` does, for an
+* event the handler decides on itself.
+*
+* ```ts
+* export const users = new Topic('Users', {
+*   events: { 'user.created': z.object({ userId: z.string() }) },
+* });
+* ```
+*/
+var Topic = class extends Construct {
+	__IS_TOPIC__ = true;
+	static isTopic(obj) {
+		return Boolean(obj && obj.__IS_TOPIC__ === true && obj.type === "dev.geekmidas.resource.topic");
+	}
+	/**
+	* The canonical id this topic is declared under.
+	*
+	* Derived from the name, so `users` and `Users` are one topic. The name is
+	* left alone: subscribers bind to it and it is what the broker routes on.
+	*/
+	id;
+	/** The name it was declared with — what the broker routes on. */
+	name;
+	/**
+	* The event contract — a map of event type → payload schema. Named
+	* `eventSchemas` (not `events`) to avoid clashing with `Construct.events`,
+	* which is the array of `MappedEvent`s a construct *publishes*.
+	*/
+	eventSchemas;
+	/**
+	* The topic as a dependency — what `.dependsOn([users])` and
+	* `.event(users, …)` dissolve into, reachable as `services.users`.
+	*
+	* The producer, because publishing is the only thing depending on a topic
+	* can mean: a subscriber binds to the topic instead, and is never handed
+	* this. It reads `<NAME>_PUBLISHER_CONNECTION_STRING` and picks the
+	* transport from its protocol — `pgboss://` locally, `sns://` deployed.
+	*
+	* A field assigned once, not a getter: services are cached by object
+	* identity, and a fresh literal on every access never hit that cache.
+	*/
+	service;
+	/** The producer's env key, read by both {@link declare} and the service. */
+	connectionKey;
+	constructor(name, options) {
+		super("dev.geekmidas.resource.topic", DEFAULT_LOGGER, [], []);
+		this.name = name;
+		this.id = canonicalId(name);
+		this.eventSchemas = options.events;
+		this.connectionKey = provideKey(this.id, "publisherConnectionString");
+		const envVar = this.connectionKey;
+		const topic = this.name;
+		this.service = {
+			serviceName: serviceKey(this.id),
+			async register({ envParser }) {
+				const { connectionString } = envParser.create((get) => ({ connectionString: get(envVar).string() })).parse();
+				return Publisher.fromConnectionString(connectionString, { topic });
+			}
+		};
+	}
+	/**
+	* What this topic is in the manifest.
+	*
+	* Only the producer's key: a subscriber is *bound* to a topic rather than
+	* depending on it, so the binding is an edge the deploy target reads and not
+	* an env key anyone can hold. Locally both sides meet on the same broker.
+	*/
+	declare() {
+		return [{
+			kind: "topic",
+			id: this.id,
+			provides: [this.connectionKey],
+			events: this.eventTypes,
+			subscribers: []
+		}];
+	}
+	/** The event type names this topic carries. */
+	get eventTypes() {
+		return Object.keys(this.eventSchemas);
+	}
+};
+//#endregion
+export { Topic as t };
+
+//# sourceMappingURL=Topic-hPffOsot.mjs.map

package/dist/Topic-hPffOsot.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"Topic-hPffOsot.mjs","names":[],"sources":["../src/topic/Topic.ts"],"sourcesContent":["import {\n\ttype EventPublisher,\n\ttype EventPublisherConnectionString,\n\ttype PublishableMessage,\n\tPublisher,\n} from '@geekmidas/events';\nimport { DEFAULT_LOGGER } from '@geekmidas/logger/console';\nimport {\n\ttype ConstructName,\n\tcanonicalId,\n\ttype Declaration,\n\tprovideKey,\n\tserviceKey,\n} from '@geekmidas/manifest';\nimport type { InferStandardSchema } from '@geekmidas/schema';\nimport type { Service } from '@geekmidas/services';\nimport type { StandardSchemaV1 } from '@standard-schema/spec';\nimport { Construct, ConstructType } from '../Construct';\n\n/** A topic's event contract — a map of event type → payload schema. */\nexport type TopicEvents = Record<string, StandardSchemaV1>;\n\n/**\n * The union of wire messages a topic carries, derived from its event map:\n * `{ type: 'user.created'; payload: … } | { type: 'user.updated'; payload: … }`.\n */\nexport type TopicMessage<TEvents extends TopicEvents> = {\n\t[K in keyof TEvents & string]: PublishableMessage<\n\t\tK,\n\t\tInferStandardSchema<TEvents[K]>\n\t>;\n}[keyof TEvents & string];\n\n/**\n * A topic — pub/sub fan-out. Unlike a `Queue` (point-to-point, one consumer), a\n * topic is a *resource* owned by no single handler: it declares the event\n * contract, and any number of subscribers (`worker.topic(topic)`) bind to it.\n * `gkm build` discovers it into the manifest's `topics` field; infra provisions\n * an SNS topic.\n *\n * A construct publishes with `.event(topic, { type, payload })`, repeatable\n * across topics, each event going through its own topic's publisher. That also\n * puts `services.<topic>` in the handler, as `.dependsOn([topic])` does, for an\n * event the handler decides on itself.\n *\n * ```ts\n * export const users = new Topic('Users', {\n *   events: { 'user.created': z.object({ userId: z.string() }) },\n * });\n * ```\n */\nexport class Topic<\n\tTName extends string = string,\n\tTEvents extends TopicEvents = TopicEvents,\n> extends Construct {\n\t__IS_TOPIC__ = true;\n\n\tstatic isTopic(obj: unknown): obj is Topic<string, TopicEvents> {\n\t\treturn Boolean(\n\t\t\tobj &&\n\t\t\t\t(obj as { __IS_TOPIC__?: boolean }).__IS_TOPIC__ === true &&\n\t\t\t\t(obj as Construct).type === ConstructType.Topic,\n\t\t);\n\t}\n\n\t/**\n\t * The canonical id this topic is declared under.\n\t *\n\t * Derived from the name, so `users` and `Users` are one topic. The name is\n\t * left alone: subscribers bind to it and it is what the broker routes on.\n\t */\n\treadonly id: string;\n\n\t/** The name it was declared with — what the broker routes on. */\n\treadonly name: TName;\n\n\t/**\n\t * The event contract — a map of event type → payload schema. Named\n\t * `eventSchemas` (not `events`) to avoid clashing with `Construct.events`,\n\t * which is the array of `MappedEvent`s a construct *publishes*.\n\t */\n\treadonly eventSchemas: TEvents;\n\n\t/**\n\t * The topic as a dependency — what `.dependsOn([users])` and\n\t * `.event(users, …)` dissolve into, reachable as `services.users`.\n\t *\n\t * The producer, because publishing is the only thing depending on a topic\n\t * can mean: a subscriber binds to the topic instead, and is never handed\n\t * this. It reads `<NAME>_PUBLISHER_CONNECTION_STRING` and picks the\n\t * transport from its protocol — `pgboss://` locally, `sns://` deployed.\n\t *\n\t * A field assigned once, not a getter: services are cached by object\n\t * identity, and a fresh literal on every access never hit that cache.\n\t */\n\treadonly service: Service<\n\t\tUncapitalize<TName>,\n\t\tEventPublisher<TopicMessage<TEvents>>\n\t>;\n\n\t/** The producer's env key, read by both {@link declare} and the service. */\n\tprivate readonly connectionKey: string;\n\n\tconstructor(name: ConstructName<TName>, options: TopicOptions<TEvents>) {\n\t\tsuper(ConstructType.Topic, DEFAULT_LOGGER, [], []);\n\n\t\tthis.name = name as TName;\n\t\tthis.id = canonicalId(name as string);\n\t\tthis.eventSchemas = options.events;\n\t\tthis.connectionKey = provideKey(this.id, 'publisherConnectionString');\n\n\t\tconst envVar = this.connectionKey;\n\t\tconst topic = this.name as string;\n\t\tthis.service = {\n\t\t\tserviceName: serviceKey(this.id) as Uncapitalize<TName>,\n\t\t\tasync register({ envParser }) {\n\t\t\t\tconst { connectionString } = envParser\n\t\t\t\t\t.create((get) => ({ connectionString: get(envVar).string() }))\n\t\t\t\t\t.parse();\n\n\t\t\t\t// Named as a topic, so a broker with one address for everything\n\t\t\t\t// (pg-boss) fans each message out to every subscriber.\n\t\t\t\treturn Publisher.fromConnectionString<TopicMessage<TEvents>>(\n\t\t\t\t\tconnectionString as EventPublisherConnectionString,\n\t\t\t\t\t{ topic },\n\t\t\t\t);\n\t\t\t},\n\t\t};\n\t}\n\n\t/**\n\t * What this topic is in the manifest.\n\t *\n\t * Only the producer's key: a subscriber is *bound* to a topic rather than\n\t * depending on it, so the binding is an edge the deploy target reads and not\n\t * an env key anyone can hold. Locally both sides meet on the same broker.\n\t */\n\tdeclare(): Declaration[] {\n\t\treturn [\n\t\t\t{\n\t\t\t\tkind: 'topic',\n\t\t\t\tid: this.id,\n\t\t\t\tprovides: [this.connectionKey],\n\t\t\t\t// The contract this topic carries. Structural: which events exist\n\t\t\t\t// is a fact about the application, and a subscriber binding to one\n\t\t\t\t// that does not is a mistake worth catching at build.\n\t\t\t\tevents: this.eventTypes,\n\t\t\t\t// Bound rather than declared here — a subscriber names the topic,\n\t\t\t\t// not the other way round — so the build fills these from what it\n\t\t\t\t// found. Nested when it does, because position is the trigger.\n\t\t\t\tsubscribers: [],\n\t\t\t},\n\t\t];\n\t}\n\n\t/** The event type names this topic carries. */\n\tget eventTypes(): (keyof TEvents & string)[] {\n\t\treturn Object.keys(this.eventSchemas) as (keyof TEvents & string)[];\n\t}\n}\n\nexport interface TopicOptions<TEvents extends TopicEvents> {\n\t/** Each event this topic carries — its type, and its payload's schema. */\n\tevents: TEvents;\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;AAmDA,IAAa,QAAb,cAGU,UAAU;CACnB,eAAe;CAEf,OAAO,QAAQ,KAAiD;EAC/D,OAAO,QACN,OACE,IAAmC,iBAAiB,QACpD,IAAkB,SAAA,8BACrB;CACD;;;;;;;CAQA;;CAGA;;;;;;CAOA;;;;;;;;;;;;;CAcA;;CAMA;CAEA,YAAY,MAA4B,SAAgC;EACvE,MAAA,gCAA2B,gBAAgB,CAAC,GAAG,CAAC,CAAC;EAEjD,KAAK,OAAO;EACZ,KAAK,KAAK,YAAY,IAAc;EACpC,KAAK,eAAe,QAAQ;EAC5B,KAAK,gBAAgB,WAAW,KAAK,IAAI,2BAA2B;EAEpE,MAAM,SAAS,KAAK;EACpB,MAAM,QAAQ,KAAK;EACnB,KAAK,UAAU;GACd,aAAa,WAAW,KAAK,EAAE;GAC/B,MAAM,SAAS,EAAE,aAAa;IAC7B,MAAM,EAAE,qBAAqB,UAC3B,QAAQ,SAAS,EAAE,kBAAkB,IAAI,MAAM,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,CAC7D,MAAM;IAIR,OAAO,UAAU,qBAChB,kBACA,EAAE,MAAM,CACT;GACD;EACD;CACD;;;;;;;;CASA,UAAyB;EACxB,OAAO,CACN;GACC,MAAM;GACN,IAAI,KAAK;GACT,UAAU,CAAC,KAAK,aAAa;GAI7B,QAAQ,KAAK;GAIb,aAAa,CAAC;EACf,CACD;CACD;;CAGA,IAAI,aAAyC;EAC5C,OAAO,OAAO,KAAK,KAAK,YAAY;CACrC;AACD"}