Expand description
The catalog as data: core.catalog.json (embedded by the generator), the
catalog ids, token groups, and the merged VIEW of the core plus registered
extensions every lookup goes through. Mirrors src/catalog.ts.
Structs§
- Catalog
View - The core merged with registered extensions. Extension names never shadow
a core name (
define_extensionrefuses that), so a plain overlay is exact.
Constants§
- A2UI_
BASIC_ CATALOG_ ID - The vendored A2UI basic catalog.
- A2UI_
VERSION - The A2UI wire
versionthe vendored schemas carry. - CORE_
CATALOG_ ID https://ui.exponential.at/catalogs/core/v1- CORE_
LITE_ CATALOG_ ID - The prompt-sized subset: a lite surface is a valid core surface.
- SUPPORTED_
CATALOG_ IDS - What a client advertises as
supportedCatalogIds. - UNKNOWN_
COMPONENT - The placeholder component painted for anything unmapped.
Statics§
- CORE
- The parsed core catalog, once per process. VAPP-106: the RUNTIME catalog,
without the model-facing descriptions and examples (
descriptions()). - CORE_
MACROS - The core macro table, once per process.
- TOKEN_
GROUPS - Token groups → names, flattened (
type.size, not nested), in source order.
Functions§
- component_
def - The component definition in the core (no extensions).
- component_
names - Component names in source order, optionally the lite subset, never the hidden placeholder.
- is_
known_ token - True when the reference names a token group AND a name in it.
- parse_
token_ ref parse_token_ref_strover a JSON value.- parse_
token_ ref_ str $spacing.md→("spacing", "md"),$type.size.sm→("type.size", "sm");Nonewhen the string is not a well-formed reference.