/**
 * ObjectUI
 * Copyright (c) 2024-present ObjectStack Inc.
 *
 * This source code is licensed under the MIT license found in the
 * LICENSE file in the root directory of this source tree.
 */
/**
 * Stored value → `<input type="date">` value (`YYYY-MM-DD`).
 *
 * A leading `YYYY-MM-DD` is passed through VERBATIM rather than re-parsed: a
 * date-only string is parsed as UTC midnight by `new Date()`, so reading local
 * calendar components back out of it shifts the day by one everywhere west of
 * Greenwich. `2026-06-17` must stay June 17th in every zone.
 */
export declare function toDateInputValue(value: unknown): string;
/**
 * Stored value → `<input type="datetime-local">` value (`YYYY-MM-DDTHH:mm`),
 * expressed in the viewer's local wall clock — the same instant the detail
 * page shows, so opening the editor never appears to move the time.
 *
 * A value that is ALREADY a zone-less local datetime is truncated to minutes
 * in place instead of being round-tripped through `Date`, which would
 * reinterpret it and then re-render it, twice risking an off-by-a-zone shift.
 */
export declare function toDateTimeInputValue(value: unknown): string;
/**
 * `<input type="datetime-local">` value → stored value (ISO-8601, UTC).
 *
 * The control hands us a zone-less local wall clock; `new Date()` reads that
 * form as local time, which is the inverse of what `toDateTimeInputValue`
 * wrote — the pair is what keeps read and write on one basis.
 *
 * An unparseable string is returned untouched rather than blanked: dropping a
 * value the user can see in the box would be a data loss dressed up as a fix.
 */
export declare function fromDateTimeInputValue(value: string): string;