[Components](https://oods-foundry.com/components) / core

# AddressCollectionPanel

Groups an address heading, summary and authored address content.

Generated from @oods/foundry 0.10.1

- Categories

  core

- Contexts

  detail

- Readiness

  `proven-in-generated-apps`

## Playground

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

Documented example `address-collection-panel-title-and-summary` : mount without authored children, h2 heading, visible subtitle and the summary text inside the content area.

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

The real AddressCollectionPanel, live

React

## Addresses

Billing and shipping

2 addresses on file

Vue

## Addresses

Billing and shipping

2 addresses on file

## Code

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

**React**

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

export function Example() {
  return (
    <AddressCollectionPanel
      title="Addresses"
      subtitle="Billing and shipping"
      summary="2 addresses on file"
    />
  );
}
```

## Props, slots and events

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

Props

| Prop | Type | Required | Documented example |
| - | - | - | - |
| `title` | `string \| undefined` | no | `Addresses` |
| `label` | `string \| undefined` | no | |
| `heading` | `string \| undefined` | no | |
| `name` | `string \| undefined` | no | |
| `subtitle` | `string \| undefined` | no | `Billing and shipping` |
| `description` | `string \| undefined` | no | |
| `metadata` | `string \| undefined` | no | |
| `summary` | `string \| undefined` | no | `2 addresses on file` |
| `text` | `string \| undefined` | no | |
| `body` | `string \| undefined` | no | |
| `emptyMessage` | `string \| undefined` | no | |

### Slots

default

### Events

none

## States

summary, content

## Accessibility

- Role

  `none`

- How it gets its name

  `heading` on `h1,h2,h3,h4,h5,h6`

### Keyboard

The contract lists no keyboard behaviour.

### Obligations in the contract

- A real h3 heading names the panel section
- Subtitle and summary text remain visible beside the heading
- The panel is noninteractive

Mirrors renderAddressCollectionPanel over renderPanelSection with data-panel-type=address: title aliases title/label/heading/name (default Addresses), subtitle aliases subtitle/description/metadata, and summary/text/body/emptyMessage fill the content area only without authored children. The saved-schema directives roleField, defaultRoleField and roleParameter are consumed by codegen and left unbound. The generic field (the addresses collection) lowers to summary, the record's addresses one line each (addressCollectionSummary; a generated workflow's store prints the same line), in every renderer and on a single screen as in a workflow.

## Tokens

The token roles this component reads.

- `panel.background`
- `panel.border`
- `panel.title`
- `panel.subtitle`

## 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.

Readiness evidence

| 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 |

AddressCollectionPanel 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": "<YourAddressCollectionPanel>",
  "oodsTraits": [
    "Addressable"
  ],
  "substitution": {
    "component": "AddressCollectionPanel",
    "react": {
      "package": "<your-package>/react",
      "version": "<exact version>",
      "export": "<YourAddressCollectionPanel>"
    },
    "vue": {
      "package": "<your-package>/vue",
      "version": "<exact version>",
      "export": "<YourAddressCollectionPanel>"
    }
  }
}
```

## 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](https://oods-foundry.com/components/address-collection-panel/manifest.json).

- **Contract**: `@oods/component-contracts@0.10.1 componentContracts.AddressCollectionPanel` `sha256:a8b93dfe3f1d…`
- **Documented example**: `@oods/component-contracts@0.10.1 sharedScenarios address-collection-panel-title-and-summary` `sha256:bc2af3ef97d1…`
- **Catalog entry (catalog_list)**: `generated/0.10.1/system/catalog.json AddressCollectionPanel` `sha256:a48b6bb5b730…`
- **React readiness**: `@oods/components-react@0.10.1 readiness AddressCollectionPanel` `sha256:a3d3b1b5980c…`
- **Vue readiness**: `@oods/components-vue@0.10.1 readiness AddressCollectionPanel` `sha256:a9edeec2360e…`
- **Prop types**: `generated/0.10.1/components/prop-types.json AddressCollectionPanel` `sha256:57585e3e734e…`