/** Minimal field-metadata shape the normalizer reads. Kept permissive so any
 *  caller's field type (e.g. the dialog's `FieldDef[]`) is accepted. */
type RefFieldMeta = Record<string, any>;
/**
 * Normalize a submit payload so that EMPTY reference fields go to the server as
 * `null` rather than as `""` or the nil UUID ("00000000-…"). A dynamic FK column
 * (e.g. products.category_id, a nullable `ref`) rejects a non-null value that
 * points at no row: sending `""`/nil-UUID triggers
 *   insert ... violates foreign key constraint "fk_products_category" (23503)
 * even though the user left the picker empty.
 *
 * Nullability decision (Fase 4): prefer the EXPLICIT `nullable` flag the kernel
 * (v0.77.1+) now serves per field (`modelbase.FieldDef.Nullable`, `!Required`).
 * When `field.nullable === true` an empty value is submitted as `null`; when
 * `field.nullable === false` the value is respected. When the flag is absent
 * (undefined — older hosts that don't serve it yet) we fall back to the legacy
 * type-based heuristic (`getFieldRef` / dynamic_select / search). This keeps
 * backward-compat while letting the contract, not a guess, drive the decision.
 *
 * The explicit flag also lets us null an empty OPTIONAL ref whose column is NOT
 * a uuid (which the uuid-only heuristic never covered). To avoid nulling a plain
 * optional text field — where `""` is a legitimate value, not "no relation" — we
 * gate the explicit path on the field ALSO looking like a reference/relation
 * (`getFieldRef` / dynamic_select / search). A nullable non-ref scalar keeps its
 * `""`. This is generic — every addon's optional relations benefit. Does not
 * mutate `values`.
 */
export declare function normalizeRefFieldsForSubmit(values: Record<string, any>, fields: RefFieldMeta[] | undefined): Record<string, any>;
export {};
//# sourceMappingURL=normalize-submit.d.ts.map