Feedback

Communicate messages, completion, and pending work with theme tokens and reduced-motion behavior.

Overview

Communicate messages, completion, and pending work with theme tokens and reduced-motion behavior.

Installation

npx @mwillbanks/tuil add alert progress spinner

The CLI writes source-owned components beneath the destination configured in tuil.config.ts; the default import below assumes src/components/tuil.

Loading executable example…

Components and subcomponents

API	Signature	Description
`Alert`	`function Alert`	Public function Alert.
`Progress`	`function Progress`	Public function Progress.
`Spinner`	`function Spinner`	Public function Spinner.

Interaction

Read-only; update props as application state changes.

API and events

No events are emitted.

Every interactive component publishes semantic roles, labels, state, and focus identity through the renderer's SemanticRegistry. Callback failures flow to the owning application's error boundary.

Documentation flow diagram. props and runtime state; semantic registration; focus and input routing; callback or state update; rerender; S0 leads to S1; S1 leads to S2; S2 leads to S3 — **Documentation flow diagram.** props and runtime state; semantic registration; focus and input routing; callback or state update; rerender; S0 leads to S1; S1 leads to S2; S2 leads to S3

Example

import type { ComponentProps } from "react";
import { Alert } from "@/components/tuil/feedback/alert";

export function Example(props: ComponentProps<typeof Alert>) {
  return <Alert {...props} />;
}

Registry-installed components are source-owned: customize the generated file in your application, and use the package reference for the shared runtime contracts.