Radiant0.3.0-rc.2

Controller Decorator Visualizer

How RadiantController turns authored HTML into a reactive surface: attributes in, events in, refs out, state in between.

Wire a host with data-controller. The controller then:

  • reads host attributes with @attr(...)
  • resolves authored refs with @query(...)
  • reacts to button input with @onEvent(...)
  • stores controller-local values with @state
  • mirrors changes back into the DOM with @onUpdated(...)

Controller decorators

A single RadiantController reads host attributes, resolves DOM refs, handles delegated events, and pushes reactive updates back into authored markup.

Initial hydrate

The host attribute seeded controller state and all queried nodes resolved on connect.

Host attributes

@controller · @attr

data-signal
ready
aria-busy
false

Delegated events

@onEvent

initial hydrate

Query surface

@query

resolved refs

0

State and updates

@state · @onUpdated

signal
ready
pulses
0

Hydrated from host attribute

The Pattern

RadiantController sits on markup you already have — server templates, CMS output, hand-written HTML — and keeps attributes, events, refs, and reactive state synchronized.

The DOM stays the structure source of truth. The controller is the behavior layer.