import type { ReactNode } from "react";
import type { AccordionHeadingLevel, AccordionItem } from "./Accordion.tsx";
export type AccordionSectionProps = {
    headingLevel: AccordionHeadingLevel;
    id: string;
    isExpanded: boolean;
    item: AccordionItem;
    onToggle: (key: string) => void;
    panelId: string;
    /**
     * `VisibilityGroup.register` or `MultiplePicker.register`,
     * whichever kind the accordion is running. Both have this shape,
     * which is the point of the kinds being separate rather than one
     * configurable one.
     */
    register: (key: string) => () => void;
};
/**
 * Its own file for the same reason `TabTrigger` is: **registration
 * is an effect**, and an effect cannot run in a loop.
 *
 * A disabled section stays out of the group entirely — it is not a
 * member, so nothing can expand it, including a consumer passing its
 * key in `expandedKeys`. That is registration-as-membership again,
 * and it is the behaviour a `<summary>` cannot have at all.
 */
export declare const AccordionSection: ({ headingLevel, id, isExpanded, item, onToggle, panelId, register, }: AccordionSectionProps) => ReactNode;
//# sourceMappingURL=AccordionSection.d.ts.map