export interface DateTimeInputProps {
    value?: Date | null;
    /** Fires with a `Date` carrying both the picked day and `HH:mm`. */
    onChange?: (value: Date | null) => void;
    placeholder?: string;
    /** Lower bound. The day is enforced on the calendar; on the boundary day the
     *  time input also gets a `min="HH:mm"` so a same-day earlier time is rejected. */
    min?: Date;
    /** Upper bound. Day enforced on the calendar; same-day time bounded via the
     *  time input's `max="HH:mm"`. */
    max?: Date;
    /** Native `<input type="time">` step, in minutes. Default `1`. */
    minuteStep?: number;
    disabled?: boolean;
    error?: string;
    className?: string;
}
/**
 * DateTimeInput — the time-aware sibling of `DatePicker`. Composes `DatePicker`
 * (branded calendar, tr/en format) + a native `<Input type="time">`, exactly as
 * `DateRangePicker` composes two `DatePicker`s. Value stays `Date | null` (a
 * superset of `DatePickerProps`) so consumers' existing Date↔string bridges keep
 * working. Changing the date preserves the current time (else 00:00); changing
 * the time preserves the current date (else today); seconds are always zeroed.
 *
 * `min`/`max` are full datetime bounds: the calendar restricts day selection at
 * day granularity (boundary days stay selectable), the emitted value is clamped
 * into `[min, max]`, and on a boundary day the time input also shows an `HH:mm`
 * bound. So picking the max day keeps a within-day time but snaps a later one to
 * `max` rather than emitting an out-of-range datetime.
 */
export declare function DateTimeInput({ value, onChange, placeholder, min, max, minuteStep, disabled, error, className, }: DateTimeInputProps): import("react").JSX.Element;
//# sourceMappingURL=DateTimeInput.d.ts.map