Playground

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

Documented example message-event-timeline-statuses : mount with statuses only, statuses supply the events when messages are absent, in the message timeline type.

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

The real MessageEventTimeline, live
React

Delivery

  1. delivered

Vue

Delivery

  1. delivered

Code

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

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

const statuses = [
  {
    "status": "delivered",
    "at": "2026-09-02T09:00:00Z"
  }
];

export function Example() {
  return (
    <MessageEventTimeline
      heading="Delivery"
      statuses={statuses}
    />
  );
}

Props, slots and events

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

Props
PropTypeRequiredDocumented example
title string | undefined no
label string | undefined no
heading string | undefined no Delivery
name string | undefined no
events readonly unknown[] | undefined no
messages readonly unknown[] | undefined no
statuses readonly unknown[] | undefined no [{"status":"delivered","at":"2026-09-02T09:00:00Z"}]

Slots

default

Events

none

States

populated, empty

Accessibility

Role
log
How it gets its name
aria-label on [role="log"]

Keyboard

The contract lists no keyboard behaviour.

Obligations in the contract

  • A log region named by its title, which is also a real h3 heading
  • Events are an ordered list with machine-readable timestamps
  • An empty timeline is named No events

Mirrors renderMessageEventTimeline over renderTimelineContainer with data-timeline-type=message and role=log: title aliases title/label/heading/name (default Message Timeline); the first array among events/messages/statuses supplies the events, each rendered as label, time and detail exactly as normalizeTimelineItems reads them (records use label/title/event/status/state/text/name, timestamp/datetime/time/at/createdAt/updatedAt and detail/description/reason/message/from/to; scalars render as text); no events renders the named empty item; authored children replace the list. messagesField lowers to messages and statusesField to statuses; messages wins over statuses when both are arrays, as in the renderer.

Tokens

The token roles this component reads.

  • timeline.background
  • timeline.border
  • timeline.text
  • timeline.marker

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.

Readiness evidence
EvidenceReactVue
stateimplemented-evidence-completeimplemented-evidence-complete
versioned contractpassedpassed
target implementationpassedpassed
package exportpassedpassed
public declarationpassedpassed
dependency closurepassedpassed
framework scenariopassedpassed
accessibilityverifiedverified
interactionnot-applicablenot-applicable
visual themesverifiedverified

MessageEventTimeline presents content and owns no focusable control or action; authored child actions remain the consumer's responsibility.

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": "<YourMessageEventTimeline>",
  "oodsTraits": [
    "<trait names>"
  ],
  "substitution": {
    "component": "MessageEventTimeline",
    "react": {
      "package": "<your-package>/react",
      "version": "<exact version>",
      "export": "<YourMessageEventTimeline>"
    },
    "vue": {
      "package": "<your-package>/vue",
      "version": "<exact version>",
      "export": "<YourMessageEventTimeline>"
    }
  }
}

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.MessageEventTimeline sha256:ea4527cb63dd…
  • Documented example: @oods/component-contracts@0.10.1 sharedScenarios message-event-timeline-statuses sha256:af81e6a538cf…
  • Catalog entry (catalog_list): generated/0.10.1/system/catalog.json MessageEventTimeline sha256:759487f9ba5c…
  • React readiness: @oods/components-react@0.10.1 readiness MessageEventTimeline sha256:7d566efb80fd…
  • Vue readiness: @oods/components-vue@0.10.1 readiness MessageEventTimeline sha256:edf71dc30fb5…
  • Prop types: generated/0.10.1/components/prop-types.json MessageEventTimeline sha256:62b51869894b…