PriceCardMeta

Playground

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

Documented example price-card-meta-inline-terms : mount, model and interval have literal inline labels; price metadata is noninteractive.

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

export function Example() {
  return (
    <PriceCardMeta
      pricingModel="flat"
      billingInterval="monthly"
    />
  );
}

Props, slots and events

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

Slots

default

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

• model and interval have literal inline labels
• price metadata is noninteractive

Mirrors renderPriceCardMeta over renderMetaInline: title/label/heading/name (default Price), Model model/pricingModel and Interval interval/billingInterval inline terms, their codes read as PriceSummary reads them (formatPriceCode: one_time reads One Time). Children replace the entire body including its title. modelField and intervalField lower to their runtime keys. amountField, currencyField and minorUnitsParameter are consumed unbound because this HTML metadata renderer has no amount or currency term. Noninteractive.

Tokens

The token roles this component reads.

• meta.text
• meta.label

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.

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

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.PriceCardMeta sha256:6d93eca22529…
• Documented example: @oods/component-contracts@0.10.1 sharedScenarios price-card-meta-inline-terms sha256:3a515f8b0ad9…
• Catalog entry (catalog_list): generated/0.10.1/system/catalog.json PriceCardMeta sha256:5274e2d9da63…
• React readiness: @oods/components-react@0.10.1 readiness PriceCardMeta sha256:c651d42b67c3…
• Vue readiness: @oods/components-vue@0.10.1 readiness PriceCardMeta sha256:c5206694c82e…
• Prop types: generated/0.10.1/components/prop-types.json PriceCardMeta sha256:a8043efb3600…