RMT Reference: Enums and Catalogs
This page lists fixed values used by operators.
Syntax
Allowed contexts
Catalog values appear in clauses that expect static values. They are not JavaScript enums and are not imported.
Parameters
All values are literal in RMT source. Trust boundaries are written as strings; the other values are usually identifiers.
Description
Catalogs keep authoring stable and inspectable. New values need tooling, docs and test coverage.
Examples
template reference.catalogs {
resource preview.file kind object-url owner surface.preview
overlay notice kind toast portal app.root
portal app.root root "#app" layer surface
transition preview.open {
trigger action preview.show
from surfaces [preview.closed]
to surfaces [preview.open]
effect crossfade
durationMs 160
easing "ease-out"
lane transition
}
action preview.show {
input id string
reduce state.preview.id = input.id
emit preview.opened with id input.id
}
state preview.id type string initial ""
surface preview kind page component x-section {
portal app.root
lane visible weight 80 {
mount preview.card from endpoint preview.card {
trust boundary "xtend.security.sanitizing-boundary.v1"
}
}
}
}
Diagnostics
Parser diagnostics check syntax and context. Catalog and semantic checks report unknown or incomplete values.
Related operators
lane, from, overlay, resource, transition, trust boundary.
Related reading
The RMT reference index explains how enum and catalog names are resolved by other records. Related article