BillingCardMeta

Playground

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

Documented example billing-card-minor-units : mount, $19.99 · monthly.

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

export function Example() {
  return (
    <BillingCardMeta
      amount={1999}
      currency="usd"
      minorUnits={100}
      interval="monthly"
    />
  );
}

Props, slots and events

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

Slots

none

Events

none

States

populated, empty

Accessibility

Role

none

How it gets its name

none on :root

Keyboard

The contract lists no keyboard behaviour.

Obligations in the contract

• Native semantic elements retain their names and content
• Billable card phrase uses integer minor units, explicit currency and interval. minorUnitsParameter resolves through the trait declaration. Zero is preserved and JPY/1 has no decimals.

Billable card phrase uses integer minor units, explicit currency and interval. minorUnitsParameter resolves through the trait declaration. Zero is preserved and JPY/1 has no decimals.

Tokens

The token roles this component reads.

• billing.text
• billing.surface
• billing.border

Readiness

The evidence recorded for this component, with its label.

proven-in-generated-apps: catalog_list gives this label when generated React and Vue apps in the runtime sweep that ships with this version both use the component. That sweep was measured on the published 0.4.1, not on this version.

BillingCardMeta 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": "<YourBillingCardMeta>",
  "oodsTraits": [
    "Billable",
    "SaaSBillingBillable"
  ],
  "substitution": {
    "component": "BillingCardMeta",
    "react": {
      "package": "<your-package>/react",
      "version": "<exact version>",
      "export": "<YourBillingCardMeta>"
    },
    "vue": {
      "package": "<your-package>/vue",
      "version": "<exact version>",
      "export": "<YourBillingCardMeta>"
    }
  }
}

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.BillingCardMeta sha256:2f1ab635e9df…
• Documented example: @oods/component-contracts@0.10.1 sharedScenarios billing-card-minor-units sha256:b8f800b16640…
• Catalog entry (catalog_list): generated/0.10.1/system/catalog.json BillingCardMeta sha256:2a488b506230…
• React readiness: @oods/components-react@0.10.1 readiness BillingCardMeta sha256:4279cd869266…
• Vue readiness: @oods/components-vue@0.10.1 readiness BillingCardMeta sha256:9076b53b914f…
• Prop types: generated/0.10.1/components/prop-types.json BillingCardMeta sha256:0985ef19bf6d…