@threadplane/renderInterfacev0.3.4

RenderConfig

Options for provideRender — the registry, state, computed functions, and action handlers the render engine uses to turn a spec into live Angular components. Every field is optional.

View source View Markdown

import type { RenderConfig } from '@threadplane/render';

Declaration

export interface RenderConfig  {
  functions?: Record<string, ComputedFunction>;
  handlers?: Record<string, (params: Record<string, unknown>) => unknown | Promise<unknown>>;
  registry?: AngularRegistry;
  store?: StateStore;
  telemetry?: boolean;
}

Members

functions

Named computed functions a spec can reference (e.g. via $compute) to derive values from state.

functions?: Record<string, ComputedFunction>;

handlers

Named action handlers invoked when interactive elements fire (e.g. a Button's onClick).

handlers?: Record<string, (params: Record<string, unknown>) => unknown | Promise<unknown>>;

registry

Component registry mapping spec element types to Angular components.

registry?: AngularRegistry;

store

Backing state store that $bindState paths read from and interactive elements write to.

store?: StateStore;

telemetry

Set false to disable automatic development browser collection for this render tree.

telemetry?: boolean;