Version: latest

Works everywhere

DynamicList works in both server and client environments. Always use the standard import (e.g. @prokodo/ui/dynamic-list) — the library detects the runtime automatically.

DynamicList

DynamicList renders a repeatable set of input rows that users can add or remove at runtime. Ideal for managing arrays of values inside forms (e.g. phone numbers, addresses, tags).

Live demo →

Overview

import { DynamicList } from "@prokodo/ui/dynamic-list"
;<DynamicList
  label="Phone numbers"
  name="phones"
  value={phones}
  onChange={setPhones}
  renderItem={(item, onChange) => (
    <Input value={item} onChange={e => onChange(e.target.value)} />
  )}
/>

Live PreviewOpen in Storybook ↗

Import

import { DynamicList } from "@prokodo/ui/dynamic-list"

CSS:

import "@prokodo/ui/dynamic-list.css"

Props

Prop	Type	Default	Required	Description
`fields`	`DynamicListField[]`	—	✅	Field definitions for each row.
`value`	`Record<string, unknown>[]`	—	—	Controlled list of row values.
`name`	`string`	—	—	Name for hidden form input.
`label`	`string`	—	—	Label text shown above the list.
`labelProps`	`LabelProps`	—	—	Props forwarded to the label element.
`disabled`	`boolean`	`false`	—	Disable all interactions.
`required`	`boolean`	`false`	—	Mark field as required.
`errorText`	`string`	—	—	Error message shown below the list.
`helperText`	`string`	—	—	Helper text shown below the list.
`color`	`Variants`	—	—	Accent color variant.
`buttonAddProps`	`ButtonProps`	—	—	Props for the "Add row" button.
`buttonDeleteProps`	`ButtonProps`	—	—	Props for each "Delete row" button.
`classNameList`	`string`	—	—	CSS class on the list wrapper.
`onChange`	`(rows: Record<string, unknown>[]) => void`	—	—	Called when rows change.
`className`	`string`	—	—	CSS class on root element.

See src/components/dynamic-list/DynamicList.model.ts for the full DynamicListProps type.

Design Tokens

Customise DynamicList via CSS custom properties on :root or a scoped ancestor.

Token	Default	Description
`--pk-dynamic-list-label-mb`	`var(--pk-space-md)`	Label bottom margin
`--pk-dynamic-list-gap`	`var(--pk-space-lg)`	Gap between list items
`--pk-dynamic-list-field-mb`	`var(--pk-space-lg)`	Field bottom margin
`--pk-dynamic-list-helper-fg`	`var(--pk-palette-grey-300)`	Helper text colour
`--pk-dynamic-list-error-fg`	`var(--pk-color-error)`	Error text colour

AIC Note

Use the standard import path in application code:

import { DynamicList } from "@prokodo/ui/dynamic-list"

No separate /client or /lazy import selection is required in consumer code.

AIC components also support a priority flag for critical above-the-fold elements. This is most visible on Image (native preloading via <link rel="preload"> for above-the-fold content).

WCAG 2.2 Status

Criterion	Name	Status	Note
1.3.1	Info and Relationships (A)	✅ Fulfilled	Semantic structure (headings, lists, labels, landmarks) must be conveyed programmatically via HTML or ARIA.
1.3.5	Identify Input Purpose (AA)	🔍 Manual review	Form fields collecting personal data must expose their purpose via the HTML autocomplete attribute.
2.1.1	Keyboard (A)	🔍 Manual review	All functionality must be operable via keyboard alone, without requiring specific timing.
2.1.2	No Keyboard Trap (A)	🔍 Manual review	Keyboard focus must never become trapped inside a component; users must always be able to navigate away using standard keys.
2.4.3	Focus Order (A)	🔍 Manual review	The keyboard focus sequence must preserve meaning and operability in the complete page integration context.
2.4.7	Focus Visible (AA)	🔍 Manual review	A visible keyboard focus indicator must be present on every interactive element. Verify against the applied product theme.
2.4.11	Focus Not Obscured (Min.) (AA)	🔍 Manual review	The focused component must not be fully hidden by sticky headers, overlays, or other positioned page elements.
3.3.1	Error Identification (A)	🔍 Manual review	Input errors must be identified and described to the user in text, not by colour alone.
3.3.2	Labels or Instructions (A)	✅ Fulfilled	Every form input requires a programmatically associated label or a visible instruction.
4.1.2	Name, Role, Value (A)	✅ Fulfilled	Name, role, and state of all interactive UI components must be programmatically determinable via native HTML semantics or ARIA.
4.1.3	Status Messages (AA)	✅ Fulfilled	Status messages (loading, success, error, progress) must reach assistive technologies without a focus change (aria-live or role='status').

Test coverage: 2 jest-axe assertion(s) across 5 test file(s) · 6 ARIA attribute occurrence(s) in source scan. Criteria marked 🔍 require manual verification in the final product integration and theme context.

Storybook

👉 Open DynamicList in Storybook

Source

src/components/dynamic-list/DynamicList.model.ts