LollipopChart
Show sequence, schedule or attribution over rows you prepared.
@luc/ui/chartsWhat it shows
Compare a magnitude across ranked categories with less visual ink than a full bar chart.
Live preview
A ranked list on horizontal rows: the same magnitude as a bar, with less ink per category.
<LollipopChart
data={[
{ label: "Equity", value: 42 },
{ label: "Credit", value: 24 },
{ label: "Rates", value: 16 },
{ label: "Gold", value: 11 },
{ label: "Cash", value: 7 },
]}
format={{ kind: "number", decimals: 0, suffix: "%" }}
height={300}
ariaLabel="Weights by block"
/>Controls
Height
A chart measures its container, so it always needs a definite height.
State
The surface the chart is in — loading, empty and error are drawn by the component.
Accessible name
A drawing is not readable by a screen reader, so it needs a name that states what it shows.
The same fixture as the live preview above; the controls change how it is drawn, not what it measures.
Code
import { LollipopChart } from "@luc/ui/charts";
<LollipopChart
data={[
{ label: "Equity", value: 42 },
{ label: "Credit", value: 24 },
{ label: "Rates", value: 16 },
{ label: "Gold", value: 11 },
{ label: "Cash", value: 7 },
]}
format={{ kind: "number", decimals: 0, suffix: "%" }}
height={300}
ariaLabel="Weights by block"
state="ready"
/>Not controllable here
series / rows— The numbers are the caller's; the fixture above is the example.
Copy for an AI agentA specification an agent can act on: the import, the setup, the chosen props, the data contract and the accessibility expectation.
Implement `LollipopChart` from Luc UI. It is: Show sequence, schedule or attribution over rows you prepared.
Import it with: import { LollipopChart } from "@luc/ui/charts";
Requires: react ^19.0.0; react-dom ^19.0.0; react-hook-form ^7.0.0 (optional, for @luc/ui/forms/react-hook-form); tailwindcss ^4.0.0; node >= 22 (repository tools). Import the stylesheet once at the app root and wrap the tree in `LucProvider`. Both come from the package that publishes @luc.
Chosen configuration: `height={300}`, `state="ready"`, `ariaLabel="Weights by block"`.
Accessibility: keep the component's own semantics. Do not re-implement its ARIA wiring, do not add roles it does not declare, and make sure every interactive element is reachable and operable from the keyboard with a visible focus state.
Styling: use Luc UI design tokens and the component's own props. Do not restyle with raw colour literals and do not override the component's internal structure with page CSS.
Motion: respect `prefers-reduced-motion`. The component already does, so do not disable it.
Reproduce this state:
```tsx
<LollipopChart
data={[
{ label: "Equity", value: 42 },
{ label: "Credit", value: 24 },
{ label: "Rates", value: 16 },
{ label: "Gold", value: 11 },
{ label: "Cash", value: 7 },
]}
format={{ kind: "number", decimals: 0, suffix: "%" }}
height={300}
ariaLabel="Weights by block"
state="ready"
/>
```Usage
The values are prepared by the caller: this component draws the points it is given and computes no statistic of its own, so units, scaling and any summary have to be settled before the data reaches it.
It is drawn by the ECharts engine.
Worked examples with real data are on the family overview: Workflow & operations
import { LollipopChart } from "@luc/ui/charts";<LollipopChart
data={[
{ label: "Equity", value: 42 },
{ label: "Credit", value: 24 },
{ label: "Rates", value: 16 },
{ label: "Gold", value: 11 },
{ label: "Cash", value: 7 },
]}
format={{ kind: "number", decimals: 0, suffix: "%" }}
height={300}
ariaLabel="Weights by block"
/>Data contract
`data` rows contain `label` and a numeric `value`; `format` describes the measure. The caller supplies the ranking and units.
Important configuration
Keep rows in the intended order, format the value, and use one semantic tone when a category is the subject.
Guidelines
When not to use
Do not use lollipops for parts of a whole without a common baseline, or for so many categories that the stems become texture.
Configuration
| Export | Kind | Signature |
|---|---|---|
LollipopChart | 13 documented props | ({ data, format, horizontal, title, description, state, height, className, ariaLabel, ariaDescription, onReady, onEvent, eager, }: LollipopChartProps) => import("@types/react").JSX.Element |
LollipopChart props
Type: LollipopChartProps
Values the compiler reads from the declaration.
| Prop | Type | Default | Notes |
|---|---|---|---|
ariaDescription? | string | undefined | — | |
ariaLabel? | string | undefined | — | |
className? | string | undefined | — | |
data | readonly { label: string; value: number; tone?: SeriesTone; }[] | — | |
description? | string | undefined | — | |
eager? | boolean | undefined | — | Create the engine on mount rather than when the surface is approached. |
format? | ChartFormat | undefined | — | |
height? | string | number | undefined | — | |
horizontal? | boolean | undefined | — | Horizontal rows read better past ~12 categories. Default `true`. |
onEvent? | ((event: EChartEvent) => void) | undefined | — | |
onReady? | ((chart: EChartsInstance) => void) | undefined | — | |
state? | ChartState | undefined | — | |
title? | string | undefined | — |
Accessibility
A chart is a picture of data, so it needs a name that states what it shows, and the numbers must exist as text somewhere on the page — in a table or a written summary — because a drawing is not readable by a screen reader and cannot be copied.
What happens on the server, and when hydration changes it.
Family
Workflow & operations
Sequence, schedule, comparison and attribution.
Related