Figma UI kit
Domain and AI

Tree view (BOM)

v1.2.1

Show and edit nested structure: assemblies, parts, task groups.

Quick usage

Import the shared component; never copy its markup into a feature. The Web TSX tab beside the live stage has a complete, working example.

import TreeView from '@/shared/components/TreeView';

Live stage and code

The live component and its controls on the left, the code on the right; change a control and the code follows: Web TSX (the component in a working example), Tailwind and HTML (the markup it renders, with its data attributes), React Native, SwiftUI and Jetpack Compose. The header theme switch drives every stage.

Props

Read from the component's source when the docs build: names and defaults from its signature, types and descriptions from its JSDoc. A blank type means the prop has no JSDoc yet.

PropTypeDefaultDescription
nodesTreeNode[]--
defaultExpandedstring[][]Node ids open on first render.
labelstring-Accessible name for the tree.

Source: frontend/src/shared/components/TreeView/TreeView.js

DOM contract

What the rendered element carries: the data attributes its styles key on, its roles and ARIA, its focus style, and whether its stylesheet draws the 44px hit boundary. Also read from the source.

Data attributesdata-dsdata-leafdata-open
Rolesrole="group"role="tree"role="treeitem"
ARIAaria-expandedaria-labelaria-level
FocusStyles :focus-visible in its own stylesheet
44px hit boundaryYes: a ::after in TreeView.module.css

Accessibility and touch

Expanders are 28px with the 44px target.

Tree

Visible height 28px. The ::after boundary adds 8px above and below, so a gloved finger lands on a 44px target while the row keeps its density.

Rules and constraints

Use it for

  • A bill of materials, a work breakdown.

Avoid

  • Never more indent than the eye can follow: depth reads by padding steps.

Constraints

  • Nest levels use --nest-1 to --nest-3, never invented shades.

More in Domain and AI