import { type ButtonHTMLAttributes, type ReactNode } from 'react';
import type { Column } from '@tanstack/react-table';
import { type TestableProps } from '../../../utils/testId';
interface TableColumnMenuContextValue {
    column: Column<unknown>;
}
export declare const useTableColumnMenuContext: () => TableColumnMenuContextValue;
export interface TableColumnMenuProps<T = unknown> extends Omit<ButtonHTMLAttributes<HTMLButtonElement>, 'color' | 'type' | 'children'>, TestableProps {
    /** Column from the header render context. */
    column: Column<T>;
    /**
     * When omitted, the menu renders the default set of items (Move left / Move
     * right / Sort submenu / Pin / Hide) the same way the design system has
     * always rendered them. When provided, the consumer takes full control of
     * the menu's contents — typically a mix of the exported item sub-components
     * (`TableColumnMenuSortItem`, `TableColumnMenuPinItem`, etc.) for per-item
     * analytics, or arbitrary `DropdownMenuItem`s for custom actions.
     */
    children?: ReactNode;
}
/**
 * Per-column header menu ("…" trigger) with an optional consumer-controlled
 * item set. The trigger `<button>` accepts the full
 * `ButtonHTMLAttributes<HTMLButtonElement>` surface (minus `color` / `type` /
 * `children`) plus `TestableProps`, so `data-analytics-id`,
 * `data-analytics-props`, `aria-*`, `id`, `ref`, and any `data-*` reach the
 * underlying DOM node directly.
 *
 * The menu collapses to `null` when no action is available for the column
 * (sorting disabled, pinning disabled, hiding disabled, and DnD disabled) —
 * matching the behavior of the legacy `TableHeadCellMenu` it replaces.
 */
export declare const TableColumnMenu: {
    <T>({ column, children, className, "data-testid": testIdProp, ...rest }: TableColumnMenuProps<T>): import("react/jsx-runtime").JSX.Element | null;
    displayName: string;
};
export {};