RadarChart
Follow the relationship rather than the value — hover a mark to read its row.
@luc/ui/chartsWhat it shows
Compare profiles across several explicitly bounded dimensions, where the overall shape matters more than any one spoke.
Live preview
Five spokes with explicit maxima, two profiles: a radar is a shape comparison, not a ranking.
<RadarChart
indicators={[
{ name: "Return", max: 5 },
{ name: "Volatility", max: 5 },
{ name: "Liquidity", max: 5 },
{ name: "Drawdown", max: 5 },
{ name: "Cost", max: 5 },
]}
series={[
{ name: "Current", tone: "accent", values: [4, 3, 4, 2, 3] },
{ name: "Target", tone: "neutral", values: [4, 2, 5, 4, 2] },
]}
height={340}
ariaLabel="Profile across five axes"
/>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 { RadarChart } from "@luc/ui/charts";
<RadarChart
indicators={[
{ name: "Return", max: 5 },
{ name: "Volatility", max: 5 },
{ name: "Liquidity", max: 5 },
{ name: "Drawdown", max: 5 },
{ name: "Cost", max: 5 },
]}
series={[
{ name: "Current", tone: "accent", values: [4, 3, 4, 2, 3] },
{ name: "Target", tone: "neutral", values: [4, 2, 5, 4, 2] },
]}
height={340}
ariaLabel="Profile across five axes"
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 `RadarChart` from Luc UI. It is: Follow the relationship rather than the value — hover a mark to read its row.
Import it with: import { RadarChart } 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={340}`, `state="ready"`, `ariaLabel="Profile across five axes"`.
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
<RadarChart
indicators={[
{ name: "Return", max: 5 },
{ name: "Volatility", max: 5 },
{ name: "Liquidity", max: 5 },
{ name: "Drawdown", max: 5 },
{ name: "Cost", max: 5 },
]}
series={[
{ name: "Current", tone: "accent", values: [4, 3, 4, 2, 3] },
{ name: "Target", tone: "neutral", values: [4, 2, 5, 4, 2] },
]}
height={340}
ariaLabel="Profile across five axes"
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: Multidimensional, network & hierarchy
import { RadarChart } from "@luc/ui/charts";<RadarChart
indicators={[
{ name: "Return", max: 5 },
{ name: "Volatility", max: 5 },
{ name: "Liquidity", max: 5 },
{ name: "Drawdown", max: 5 },
{ name: "Cost", max: 5 },
]}
series={[
{ name: "Current", tone: "accent", values: [4, 3, 4, 2, 3] },
{ name: "Target", tone: "neutral", values: [4, 2, 5, 4, 2] },
]}
height={340}
ariaLabel="Profile across five axes"
/>Data contract
`indicators` define each spoke's name and maximum; every `series` supplies one value per indicator in the same order. The maxima are part of the visual scale and must be supplied.
Important configuration
Set meaningful indicator maxima, keep axis order consistent, and use at most a few series so overlaps remain readable.
Guidelines
When not to use
Do not use radar to rank observations or to compare profiles with different maxima as if the areas were commensurable.
Configuration
| Export | Kind | Signature |
|---|---|---|
RadarChart | 12 documented props | ({ indicators, series, format, title, description, state, height, className, ariaLabel, ariaDescription, onReady, onEvent, }: RadarChartProps) => import("@types/react").JSX.Element |
RadarChart props
Type: RadarChartProps
Values the compiler reads from the declaration.
| Prop | Type | Default | Notes |
|---|---|---|---|
ariaDescription? | string | undefined | — | |
ariaLabel? | string | undefined | — | |
className? | string | undefined | — | |
description? | string | undefined | — | |
format? | ChartFormat | undefined | — | |
height? | string | number | undefined | — | |
indicators | readonly RadarIndicator[] | — | |
onEvent? | ((event: EChartEvent) => void) | undefined | — | |
onReady? | ((chart: EChartsInstance) => void) | undefined | — | |
series | readonly RadarSeries[] | — | |
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
Multidimensional, network & hierarchy
When the relationship, not the value, is the finding.
Related