@roxyapi/ui-vue 0.34.0 → 0.36.0

package/dist/utils/compact.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Turn a compact API response back into the plain shape the components render.
+ *
+ * @remarks
+ * Asking a Remote MCP tool for a compact result trades repeated field names for a header: an array of same-shaped objects arrives as `{ __cols: [names], __rows: [[values]] }`, which costs an agent far fewer tokens to read and carries exactly the same data. This is the decoder, applied at every depth, so a compact result renders in a component with nothing else to do.
+ *
+ * Every data component runs it on the way in, so a page that sets `data` from a tool result needs no call of its own. It is exported for the paths that hold the JSON before an element does.
+ *
+ * A value with nothing encoded in it is returned unchanged, by reference.
+ *
+ * @example
+ * ```ts
+ * expandCompact({ aspects: { __cols: ['a', 'b'], __rows: [['sun', 'moon'], ['sun', 'mars'], ['moon', 'mars']] } });
+ * // { aspects: [{ a: 'sun', b: 'moon' }, { a: 'sun', b: 'mars' }, { a: 'moon', b: 'mars' }] }
+ * ```
+ */
+export declare function expandCompact<T>(value: T): T;
+//# sourceMappingURL=compact.d.ts.map

package/dist/utils/compact.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"compact.d.ts","sourceRoot":"","sources":["../../src/utils/compact.ts"],"names":[],"mappings":"AAqDA;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,aAAa,CAAC,CAAC,EAAE,KAAK,EAAE,CAAC,GAAG,CAAC,CAE5C"}

package/dist/utils/tool-component.d.ts

@@ -0,0 +1,28 @@
+import { type ToolComponentEntry } from '../generated/tool-components.js';
+/** The component that renders one MCP tool result, plus the name it was matched on. */
+export interface ToolComponent extends ToolComponentEntry {
+    /** The name the lookup resolved, with any server prefix removed. */
+    toolName: string;
+}
+/**
+ * The component that renders the result of one MCP tool call, or `undefined` when nothing in the library draws that shape.
+ *
+ * @remarks
+ * The name is what every model vendor hands back beside a tool result, so it is the key this resolves on. A host is free to prefix it with the server the tool came from and a colon; ours never contain one, so everything up to the last colon is dropped before the lookup.
+ *
+ * The table is resolved at build time, so this is a property read rather than a scan and the browser carries only the four fields a caller acts on.
+ *
+ * The result is a `data` consumer like any other: parse the JSON out of the tool result, set it on the element, and set the `attrs` beside it.
+ *
+ * @example
+ * ```ts
+ * const found = componentForTool('post_tarot_spreads_three_card');
+ * if (found) {
+ *   const el = document.createElement(found.tag);
+ *   for (const [name, value] of Object.entries(found.attrs ?? {})) el.setAttribute(name, value);
+ *   el.data = JSON.parse(result.content[0].text);
+ * }
+ * ```
+ */
+export declare function componentForTool(name: string): ToolComponent | undefined;
+//# sourceMappingURL=tool-component.d.ts.map

package/dist/utils/tool-component.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"tool-component.d.ts","sourceRoot":"","sources":["../../src/utils/tool-component.ts"],"names":[],"mappings":"AAAA,OAAO,EAEN,KAAK,kBAAkB,EACvB,MAAM,iCAAiC,CAAC;AAEzC,uFAAuF;AACvF,MAAM,WAAW,aAAc,SAAQ,kBAAkB;IACxD,oEAAoE;IACpE,QAAQ,EAAE,MAAM,CAAC;CACjB;AAED;;;;;;;;;;;;;;;;;;;GAmBG;AACH,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,MAAM,GAAG,aAAa,GAAG,SAAS,CAKxE"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@roxyapi/ui-vue",
-  "version": "0.34.0",
+  "version": "0.36.0",
   "description": "Vue components for the RoxyAPI catalog. Drop-in charts, tables, cards, forms for astrology, tarot, numerology, biorhythm, I Ching, and more. One key, beautiful in 30 minutes.",
   "type": "module",
   "main": "./dist/index.cjs",