import { type MouseEventHandler, type ReactNode } from 'react';
export interface AppProviderProps {
    /**
     * Where this app keeps a person's picture. `Avatar` asks it, with the
     * person's name, whenever it is handed no picture — and so does every part
     * that draws a face through it: `Person`, `AvatarGroup`, `MembersPill`,
     * `MembersDialog`, `PersonTrigger`, `IdentityMenu`.
     */
    pictureFor?: (name: string) => string | null | undefined;
    /**
     * How this app changes page without reloading. A plain click on a link to
     * this app's own address calls it with the link's path (`/message/1`, also
     * when the `href` is the whole `https://…` address) instead of loading the
     * page again: `Link` (and so `Card` and `Breadcrumb`'s crumbs),
     * `NavItem` (and so `NavTree`'s rows), `RailItem`, `Chip`, `InlineChip`, and
     * `IconButton` (and so `ToolbarLink`).
     */
    navigate?: (href: string) => void;
    children: ReactNode;
}
type AppSetup = Omit<AppProviderProps, 'children'>;
/**
 * What every part needs to know about the app it is in, said once at the top:
 * where a person's picture comes from, and how to change page.
 *
 * Without it each app wrapped the parts that needed either: Peek's own
 * `Avatar` and `Person` only looked a picture up, and Peek's and Ship's own
 * `NavItem` only stopped a reload (Katerina, 8 October: "we would handle these
 * in estiva-ui so we don't keep copies"). Both are optional, and a part
 * without a provider above it draws exactly as it did.
 */
export declare function AppProvider({ pictureFor, navigate, children }: AppProviderProps): import("react").JSX.Element;
/** The app's picture lookup, or nothing outside an `AppProvider`. */
export declare function usePictureFor(): AppSetup['pictureFor'];
/**
 * A link's click, kept inside the app: the caller's own `onClick` first, then,
 * on a plain left click to this app's own address, the app's `navigate` in
 * place of a page load.
 *
 * Left to the browser, as an `<a>` always is: a click the caller already
 * handled (`preventDefault`), a click with a modifier or another button (a new
 * tab), a link that opens elsewhere (`target`) or downloads, and an address on
 * another site or in another scheme (`folder:`, `mailto:`). So an app that
 * still passes its own router `onClick`, as Ship's `linkTo` does, is unchanged.
 */
export declare function useInAppClick<E extends HTMLElement>(href: string | undefined, onClick?: MouseEventHandler<E>): MouseEventHandler<E> | undefined;
export {};
//# sourceMappingURL=AppProvider.d.ts.map