import React from 'react';
export interface SidebarProps extends React.HTMLAttributes<HTMLElement> {
    /**
     * Names the navigation landmark. Required: a page with a sidebar usually has
     * a second `<nav>` too, and "navigation, navigation" tells nobody which is
     * which.
     */
    label: string;
    /**
     * Pinned above the scrolling body — a workspace switcher, a search trigger,
     * icon buttons. Any component.
     */
    header?: React.ReactNode;
    /**
     * Pinned below the scrolling body — an Invite button, help, a trial notice.
     * Any component.
     */
    footer?: React.ReactNode;
    /**
     * `SidebarSection`s, and anything that sits between them — a `Divider`, a
     * promotional card. Items themselves always go inside a section.
     */
    children?: React.ReactNode;
}
export interface SidebarSectionProps extends Omit<React.HTMLAttributes<HTMLDivElement>, 'title'> {
    /** The group's name — "Spaces", "Favorites". Omit for the top group. */
    title?: string;
    /** Lets the title fold the section away. Needs a `title`. */
    isCollapsible?: boolean;
    /** Uncontrolled: whether a collapsible section starts open. */
    defaultExpanded?: boolean;
    /** Controlled: whether a collapsible section is open. */
    isExpanded?: boolean;
    onExpandedChange?: (isExpanded: boolean) => void;
    /**
     * Controls beside the title — a `+` Button to create a space. Icon-only
     * buttons need their own `aria-label`.
     */
    actions?: React.ReactNode;
    /** `SidebarItem`s only — the section renders a list. */
    children?: React.ReactNode;
}
export interface SidebarItemProps extends Omit<React.LiHTMLAttributes<HTMLLIElement>, 'onClick'> {
    /**
     * The item's text. A string, because it also names the expand button of an
     * item that has children.
     */
    label: string;
    /** Leading icon. Decorative — `label` names the item. */
    icon?: React.ReactNode;
    /** Where it goes. Omit for an item that only groups its children. */
    href?: string;
    /** For an item that acts rather than navigates. Ignored with `href`. */
    onPress?: () => void;
    /** The page the user is on. Marked `aria-current="page"`. */
    isCurrent?: boolean;
    isDisabled?: boolean;
    /** Trailing text — a count, a shortcut, a status. */
    badge?: React.ReactNode;
    /**
     * Controls for this row — `…` and `+`. Revealed on hover and whenever focus
     * is inside the row; always shown on touch screens. Icon-only buttons need
     * their own `aria-label`.
     */
    actions?: React.ReactNode;
    /**
     * Uncontrolled: whether the children start open. Defaults to open when the
     * current page is somewhere inside.
     */
    defaultExpanded?: boolean;
    /** Controlled: whether the children are open. */
    isExpanded?: boolean;
    onExpandedChange?: (isExpanded: boolean) => void;
    /** Nested `SidebarItem`s. Their presence is what makes the item expandable. */
    children?: React.ReactNode;
}
/**
 * Sidebar — an application's navigation, as a column.
 *
 * DISCLOSURE NAVIGATION, NOT `role="tree"`
 *
 * A file-tree look invites the tree role, and the tree role is wrong here.
 * A treeview takes the arrow keys, allows one tab stop for the whole widget,
 * and does not permit interactive content inside an item — so the `…` and `+`
 * buttons on a row, which are half the point of a workspace sidebar, could not
 * exist in it. This is the WAI-ARIA disclosure navigation pattern instead:
 * nested lists of links, each expandable level behind a real button with
 * `aria-expanded`, and everything reachable with Tab.
 *
 * AN ITEM THAT IS A LINK AND HAS CHILDREN GETS TWO CONTROLS
 *
 * A button cannot sit inside a link. So a row that navigates AND expands
 * renders the link and a separate chevron button beside it; a row with no
 * `href` is one button that expands. The actions slot is a sibling of both,
 * never nested inside either.
 *
 * THE CURRENT PAGE IS NEVER FOLDED AWAY
 *
 * An item whose subtree contains the current page starts open. A sidebar that
 * loads with the user's location collapsed inside a closed group tells a
 * sighted user nothing and a screen-reader user less.
 *
 * Expansion is per item, controlled or not. Remembering it across visits is the
 * caller's job — this component cannot know where that state should live.
 */
export declare const Sidebar: React.ForwardRefExoticComponent<SidebarProps & React.RefAttributes<HTMLElement>>;
export declare const SidebarSection: React.ForwardRefExoticComponent<SidebarSectionProps & React.RefAttributes<HTMLDivElement>>;
export declare const SidebarItem: React.ForwardRefExoticComponent<SidebarItemProps & React.RefAttributes<HTMLLIElement>>;
//# sourceMappingURL=Sidebar.d.ts.map