Playground

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

Documented example badge-status : mount, visible status text and decorative icon treatment.

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

The real Badge, live
React
Past due
Vue
Past due

Code

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

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

export function Example() {
  return (
    <Badge
      content="Past due"
      tone="critical"
      emphasis="solid"
    />
  );
}

Props, slots and events

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

Props
PropTypeRequiredDocumented example
content ReactNode no Past due
status string | undefined no
domain string | undefined no
tone ComponentTone | undefined no critical
emphasis ComponentEmphasis | undefined no solid
icon ReactNode no

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

  • Inline noninteractive status label
  • Decorative icons are hidden from assistive technology

The existing React status registry is the starting implementation.

Tokens

The token roles this component reads.

  • badge.background
  • badge.text
  • badge.icon

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

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

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.Badge sha256:2b5c2f8d06f6…
  • Documented example: @oods/component-contracts@0.10.1 sharedScenarios badge-status sha256:6025db6e2f1a…
  • Catalog entry (catalog_list): generated/0.10.1/system/catalog.json Badge sha256:707f6eaab14d…
  • React readiness: @oods/components-react@0.10.1 readiness Badge sha256:952d7f19ca14…
  • Vue readiness: @oods/components-vue@0.10.1 readiness Badge sha256:4efd1e1bb0b2…
  • Prop types: generated/0.10.1/components/prop-types.json Badge sha256:198bdaeffc3f…