#genui package
#Classes
|
Class |
Description |
|---|---|
#Functions
|
Function |
Description |
|---|---|
|
Build a single-Text fallback message stream from a plain string. Used by transports / | |
|
Build a Card-wrapped Text fallback message stream from a plain string. Used when the agent emits text payloads with | |
|
executeFunctionCall(processor, fn, surfaceId, dataContextPath, options) |
Resolve arguments, look the function up in the registry, and invoke it. When no impl is registered, log once and return |
|
extractCatalogComponentsFromTypeDocProject(project, options) | |
|
Normalize an arbitrary payload (string, array, object) into a flat list of | |
|
prepareMessagesForProcessing(rawMessages, messageId, activeSurfaceIds) |
Tag messages with the given messageId and report whether any of them carries a non-empty |
|
Manual escape hatch for consumers who build their own renderer and don't go through | |
|
resolveDynamicValue(processor, value, surfaceId, dataContextPath, options) | |
|
resolveFunctionArguments(processor, args, surfaceId, dataContextPath, options) | |
|
Evaluate an input component's | |
|
useDataBinding(dynamicValue, surface, dataContextPath, fallbackValue) | |
|
useResolvedProps(properties, surface, dataContextPath, processor, functions) | |
|
Bootstrap TypeDoc once and emit both component and function catalog files. Preferred entry point for the CLI — running the conversion twice doubles cold-start latency on large catalogs. | |
#Interfaces
|
Interface |
Description |
|---|---|
|
A function discovered in source via | |
|
A v0.9 | |
|
Runtime context passed to client-side function implementations. It mirrors the small DataContext subset used by upstream A2UI basic functions while staying tied to this renderer's | |
|
A pure append-only buffer of raw protocol messages produced by the developer's IO module. The store knows nothing about the v0.9 protocol — it does not parse, process, or interpret messages. It only:
Protocol-aware processing — surfaces, signals, resources, action dispatch — is the responsibility of | |
#Variables
|
Variable |
Description |
|---|---|
|
The A2UI 0.9 basic-catalog function implementations packaged as | |
#Type Aliases
|
Type Alias |
Description |
|---|---|
|
Function implementations live on the client; the agent only references functions by name. The registry is the bridge from the wire-level | |

