Accordion

A disclosure group composed from independently styleable header, trigger, and panel parts.

Like every gpui-base primitive, Accordion supplies behavior and semantic structure without imposing a product visual language. Apply GPUI styles and compose the exported parts to match your design system.

#Example

The single native Cargo entrypoint selects this primitive from the shared showcase implementation. The same showcase is compiled once for the WASM preview above.

cargo run -p gpui-base-examples -- accordion

#Import

use gpui_kit::base::{Accordion, AccordionHeader, AccordionItem, AccordionPanel, AccordionTrigger};

#Anatomy and API

The example composes Accordion, AccordionHeader, AccordionItem, AccordionPanel, AccordionTrigger. GPUI’s standard styling and event traits provide presentation; these base types provide the interaction structure.

The authoritative module is components/accordion.rs. Native and browser previews compile this same file.

#State and events

Controlled by AccordionItem::open; AccordionTrigger::on_change reports the next expanded state.

Keep controlled state on the parent render type or in a GPUI entity. Update it in callbacks and call cx.notify(); do not recreate persistent entities during every render.

#Complete Rust example

The complete implementation used by the runnable showcase is embedded directly from Rust source:

<<< ../../../crates/base/examples/showcase/components/accordion.rs{rust}

The command above supplies application initialization, window creation, and shared BaseShowcase state.

#Accessibility

Name every trigger, expose expanded state, and remove collapsed panel content from the focus order.

#Notes

Use stable element IDs where accepted. Verify focus, hover, active, selected, disabled, reduced-motion, and high-contrast appearances in the consuming design system.