Stack

Playground

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

Documented example stack-wrapped-row : resize to phone width, children wrap in DOM order.

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

export function Example() {
  return (
    <Stack
      direction="row"
      gap="sm"
      align="center"
      wrap={true}
    >
      <div>Primary</div>
      <div>Secondary</div>
    </Stack>
  );
}

Props, slots and events

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

Slots

default

Events

none

States

row, column, wrapped

Accessibility

Role

none

How it gets its name

none on :root

Keyboard

The contract lists no keyboard behaviour.

Obligations in the contract

• Does not alter child semantics

Maps saved-schema stack and inline modes to one flex primitive; patternComponent and fields are executed composition directives. Trait recipe directives authored on pattern-group Stacks are consumed by codegen: channelsField, templatesField, policiesField, conversationsField, labelField and showActor are left unbound (a layout container reads no data and the lowered StatusTimeline never governed them), while historyField and showReason travel with the lowering to the StatusTimeline whose contract governs them. Two more authoring leftovers are consumed unbound: the form composer leaves as on a Stack when it expands a heading title slot into several components, and a pattern-group Stack restates its first fields entry as a generic field; a layout container renders neither.

Tokens

The token roles this component reads.

• layout.gap

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.

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

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.Stack sha256:a5a9e29f3328…
• Documented example: @oods/component-contracts@0.10.1 sharedScenarios stack-wrapped-row sha256:0d90b9f40267…
• Catalog entry (catalog_list): generated/0.10.1/system/catalog.json Stack sha256:ab5b454dc272…
• React readiness: @oods/components-react@0.10.1 readiness Stack sha256:b2233229ccb7…
• Vue readiness: @oods/components-vue@0.10.1 readiness Stack sha256:34f4afe16221…
• Prop types: generated/0.10.1/components/prop-types.json Stack sha256:e3a73964e923…