StateTransitionEvent

Playground

This component's contract doesn't list typed props, so the playground shows its documented example.

Documented example StateTransitionEvent : mount and declared input triggers, Declared history order, from/to states, actor and reason remain visible; showActor/showReason suppress their respective details. No history is invented..

The render follows the page's theme switch: light, dark or high contrast. Both frameworks render the same example.

Code

The documented example. HTML is the markup the React component renders for it, which @oods/component-styles styles.

import { StateTransitionEvent } from '@oods/components-react';
import '@oods/component-styles/css';

const history = [
  {
    "from_state": "draft",
    "to_state": "active",
    "transitioned_at": "2026-09-01T12:00:00Z",
    "actor_id": "operator-1",
    "reason": "Approved"
  }
];

export function Example() {
  return (
    <StateTransitionEvent
      history={history}
    />
  );
}

Props, slots and events

Contract version 1.1.0. Types are from the React declarations in @oods/components-react.

Slots

none

Events

none

States

empty, populated

Accessibility

Role

article

How it gets its name

aria-label on [data-oods-component="StateTransitionEvent"]

Keyboard

The contract lists no keyboard behaviour.

Obligations in the contract

• Visible text exposes values without relying on color
• Named semantic container or noninteractive span

Declared history order, from/to states, actor and reason remain visible; showActor/showReason suppress their respective details. No history is invented; with no history the card renders nothing (s223-m01).

Tokens

The token roles this component reads.

• surface.panel
• text.body

Readiness

The evidence recorded for this component, with its label.

react-and-vue: catalog_list gives this label when the React and Vue components have complete readiness evidence, but the sweep's generated apps don't use the component in both.

StateTransitionEvent presents declared trait values and owns no focusable control or consumer action.

Use your own

You can replace this component with your own React or Vue component. Map it, and generated code imports yours at the exact version you name. A contract report, run in a real browser, lists what your component met, what it didn't, and what wasn't checked.

The component_map call, with the parts in angle brackets yours to fill:

{
  "action": "create",
  "apply": true,
  "externalSystem": "<your design system>",
  "externalComponent": "<YourStateTransitionEvent>",
  "oodsTraits": [
    "<trait names>"
  ],
  "substitution": {
    "component": "StateTransitionEvent",
    "react": {
      "package": "<your-package>/react",
      "version": "<exact version>",
      "export": "<YourStateTransitionEvent>"
    },
    "vue": {
      "package": "<your-package>/vue",
      "version": "<exact version>",
      "export": "<YourStateTransitionEvent>"
    }
  }
}

How this page was made

Generated at build from the published data, each source with the hash of what was read. The page's manifest.

• Contract: @oods/component-contracts@0.10.1 componentContracts.StateTransitionEvent sha256:af7d6e5d37b0…
• Documented example: @oods/component-contracts@0.10.1 sharedScenarios StateTransitionEvent sha256:cf71e5afd59b…
• Catalog entry (catalog_list): generated/0.10.1/system/catalog.json StateTransitionEvent sha256:afd8bd0d4cc3…
• React readiness: @oods/components-react@0.10.1 readiness StateTransitionEvent sha256:7c60e52399a6…
• Vue readiness: @oods/components-vue@0.10.1 readiness StateTransitionEvent sha256:b525649e52f5…
• Prop types: generated/0.10.1/components/prop-types.json StateTransitionEvent sha256:4da78ffeaf2f…