Data & Comparison
Chart
Chart wraps charting primitives with Kamod design tokens. Help people compare information without losing labels, units or context. Build the empty and loading states alongside the populated example. Import it from @/components/kamod-ui/chart.
Source · Design reference · API reference · Theming · Styles
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthInstallation
Import Chart from @/components/kamod-ui/chart and pass series plus config.
pnpm add @kamod-ch/uiCopy an example with @kamod-ch/ui or the matching @kamod-ch/ui/… subpath. The code block switches between those two installs. Connect The Global Theme CSS and Tailwind Source Detection before your first render.
Usage
Use semantic labels and concise legends to keep visualizations understandable.
import { Chart } from "@kamod-ch/ui";Choose a complete composition from the examples below; required child components and props vary by pattern.
Component Examples & Variants
Explore Chart in Different Contexts, from the starting pattern to the compositions below. Begin with Line Chart, then compare the examples that match your content, state and layout. These are working patterns to adapt, not a list of interchangeable variant values: check the API Reference before using a prop or combining behaviors. Look at the surrounding labels, supporting text and spacing as well as the component itself.
Read the Result and Its Implementation Together. Use each showcase’s Code view to inspect imports and composition, or its Prompt view to prepare a setup or adaptation brief. Try the narrow preview and local theme controls before connecting real data, and use Reset to return an example to its initial state. Keep layout changes in class utilities where appropriate; follow the Component Styles Guide for hierarchy and the Theming Guide for shared surfaces and colors. The Accessibility Notes explain what to preserve when making those changes.
Line Chart
Emphasize Change Across an Ordered Series. A line chart connects successive observations so the reader can follow change across the horizontal axis. Configure the series around a meaningful sequence and use labels that explain both the measured value and its interval.
Provide a readable summary or data alternative outside the graphic, and test missing values rather than silently treating absent measurements as zero.
import { Chart } from "@kamod-ch/ui";
const points = [
{ month: "Jan", value: 18 },
{ month: "Feb", value: 27 },
{ month: "Mar", value: 23 }
];
export const Example = () => <Chart type="line" data={points} xKey="month" yKey="value" />;Bar Chart
Make Category Comparisons Easy to Read. A bar chart makes differences between categories visible through a shared baseline. Configure each bar around a comparable measure, keeping the category label and value close enough that readers can interpret the comparison without guessing.
Explain the important takeaway in nearby text and provide access to the underlying values, especially when the chart summarizes information needed to make a decision.
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthProps and Data
Configure Chart using the contracts below. Read the documented options alongside the Source Definitions to understand which values your application supplies and which details the component owns. Start with a prop or helper, then follow its type link to inspect the declaration without leaving the page.
Props, slots and variants for this component.
Type cards are extracted from this checkout’s TypeScript source at build time. Props inherited through HTMLAttributes, Omit or variant helpers remain references in those declarations; their fields are not flattened here. Match the reference to your installed version, and check a package’s exports before writing an import type. A type exported by a source file is not necessarily re-exported by @kamod-ch/ui.
Component Props
? means a field can be omitted; it does not promise a fallback value. Existing documented defaults remain alongside the descriptions. For callbacks, check the argument and return types before connecting your own state or services.Chart
ChartProps
| Prop / type | Description |
|---|---|
children | Configure
|
class | Configure
|
description | Configure
|
title | Configure
|
Data Type Reference
Expand a card to inspect and copy the exact declaration. The code header identifies its repository file; follow imported or inherited types in the Implementation Source when you need the complete dependency chain. Required-field summaries cover fields declared directly in that type. Source-only helpers and inferred schema outputs describe the local implementation, not additional props you can pass to every component.
Chart Props
3 declared fieldsChartPropsChart.tsx. Referenced types retain their original names; inspect that file for imports and supporting definitions. Inspect the Complete Definition of ChartProps before adapting it.Accessibility
The core Chart component is a presentation wrapper with an optional h3 title and description. It does not inspect child graphics, generate a data table or supply keyboard interaction for a charting engine.
You have the pieces. Put them into one real interaction, keep its state in one place, and check the result with the content your application will actually show.
Connect the Foundation
Return to Choose and Compose Components to connect this reference to a working screen. Keep global CSS in one entrypoint and import only the components that screen needs.
Build the Surrounding Screen
Find a neighboring interaction in the Component Library, or start with a complete Block. Replace sample content and destinations before refining the layout; a local class change can stay with the composition.
Make the Result Hold Up
Use shared theme roles for changes that belong everywhere. Then review the whole journey: keyboard focus, long labels, narrow screens and a clear way to recover when something fails.
Keep a link to the source and note your intentional changes. Your next edit should begin with a clear decision, not another search.