Components / primitive
Badge
Displays a short label with a semantic status treatment.
Generated from @oods/foundry 0.10.1
- Categories
- primitive, visual
- Contexts
- card, detail, list
- Readiness
react-and-vue
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.
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.
| Prop | Type | Required | Documented 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
noneon: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.backgroundbadge.textbadge.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.
| Evidence | React | Vue |
|---|---|---|
| state | implemented-evidence-complete | implemented-evidence-complete |
| versioned contract | passed | passed |
| target implementation | passed | passed |
| package export | passed | passed |
| public declaration | passed | passed |
| dependency closure | passed | passed |
| framework scenario | passed | passed |
| accessibility | verified | verified |
| interaction | not-applicable | not-applicable |
| visual themes | verified | verified |
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.Badgesha256:2b5c2f8d06f6… - Documented example:
@oods/component-contracts@0.10.1 sharedScenarios badge-statussha256:6025db6e2f1a… - Catalog entry (catalog_list):
generated/0.10.1/system/catalog.json Badgesha256:707f6eaab14d… - React readiness:
@oods/components-react@0.10.1 readiness Badgesha256:952d7f19ca14… - Vue readiness:
@oods/components-vue@0.10.1 readiness Badgesha256:4efd1e1bb0b2… - Prop types:
generated/0.10.1/components/prop-types.json Badgesha256:198bdaeffc3f…