MessageStatusBadge

Playground

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

Documented example message-status-badge-delivery : mount, delivery doubles as the visible label and the status in the message variant.

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 { MessageStatusBadge } from '@oods/components-react';
import '@oods/component-styles/css';

export function Example() {
  return (
    <MessageStatusBadge
      delivery="delivered"
    />
  );
}

Props, slots and events

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

Slots

default

Events

none

States

subtle, solid

Accessibility

Role

none

How it gets its name

none on :root

Keyboard

The contract lists no keyboard behaviour.

Obligations in the contract

• Inherits Badge inline noninteractive status label semantics
• The resolved label is always visible text

Mirrors renderMessageStatusBadge over renderBadgePrimitive with default variant message and default label Message: the label reads label/text/status/delivery/value in that order, the status reads status/state/delivery/value, and both are exposed as data-badge-status and data-badge-variant on the governed Badge substrate; tone and emphasis retain their shared Badge behaviour. The saved-schema directive statusesField is consumed and left unbound: the HTML renderer reads no statuses collection.

Tokens

The token roles this component reads.

• badge.background
• badge.text

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.

MessageStatusBadge 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": "<YourMessageStatusBadge>",
  "oodsTraits": [
    "Communicable"
  ],
  "substitution": {
    "component": "MessageStatusBadge",
    "react": {
      "package": "<your-package>/react",
      "version": "<exact version>",
      "export": "<YourMessageStatusBadge>"
    },
    "vue": {
      "package": "<your-package>/vue",
      "version": "<exact version>",
      "export": "<YourMessageStatusBadge>"
    }
  }
}

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.MessageStatusBadge sha256:c29569049417…
• Documented example: @oods/component-contracts@0.10.1 sharedScenarios message-status-badge-delivery sha256:901a2ee48e73…
• Catalog entry (catalog_list): generated/0.10.1/system/catalog.json MessageStatusBadge sha256:07f7bc227122…
• React readiness: @oods/components-react@0.10.1 readiness MessageStatusBadge sha256:b3864321dcd0…
• Vue readiness: @oods/components-vue@0.10.1 readiness MessageStatusBadge sha256:653a429d96c2…
• Prop types: generated/0.10.1/components/prop-types.json MessageStatusBadge sha256:cf150b6f9c3f…