Glossário

Glossary

Async validator — a validator (onChangeAsync/onBlurAsync/onSubmitAsync/onDynamicAsync) that returns a promise, with built-in debouncing via *AsyncDebounceMs (Ch 8).

canSubmit — a derived boolean on form.state indicating whether the form is currently submittable (Ch 28).

createFormHook — the recommended way to pre-bind custom field/form components to a form context once per app/design-system, yielding useAppForm/withForm (Ch 20).

DeepKeys / DeepValue — utility types computing every valid dot-path field name for a nested object type, and the value type at a given path, respectively — the basis of the library's compile-time field-name checking (Ch 28).

Derived state — computed form-state fields like isValid/canSubmit, layered on top of BaseFormState rather than stored directly (Ch 28).

Field group — see FormGroup.

FieldApi — the framework-agnostic class representing one field's runtime state and methods (setValue, array mutators, validate, handleChange/handleBlur) (Ch 26).

field.state — a field's current value plus metadata (isTouched, isDirty, isBlurred, errors) (Ch 7).

FormApi — the framework-agnostic class representing a form instance's runtime state and methods (handleSubmit, setFieldValue, array mutators, reset) (Ch 26).

FormGroup — a component scoping a subset of fields into an independently-validated, independently-submittable sub-form, used for multi-step wizards (Ch 12).

Headless — ships no UI components; the caller renders every input and binds it to field state manually (Ch 1).

Listener — a side-effect callback (onChange/onBlur/onMount/onSubmit/onUnmount) distinct from a validator, used for auto-save or cascading field resets, not validation (Ch 15).

mergeForm — a helper that overlays server-provided partial state onto a client form instance, preserving the client form's validator configuration; core to SSR integration (Ch 22, Ch 27).

onChangeListenTo / onBlurListenTo — validator options declaring which other fields' changes should re-trigger this field's validation, enabling cross-field checks like "confirm password" (Ch 13).

onDynamic — a validator mode, paired with revalidateLogic(), allowing different validation timing before vs. after a form's first submit attempt (Ch 9).

revalidateLogic — configures mode/modeAfterSubmission for onDynamic validation (Ch 9).

ServerValidateError — the error type createServerValidate-based server validation throws on failure, caught explicitly in each meta-framework's server entry point (Ch 22).

Standard Schema — a shared validation-library interface (implemented by Zod, Valibot, ArkType, Effect/Schema) that TanStack Form accepts directly as a validator with no adapter (Ch 8).

Store / useSelector / form.Subscribe — the reactive-subscription primitives: store is the underlying state container, useSelector reads a slice for use in component logic, form.Subscribe isolates a UI re-render to a slice (Ch 14).

Updater<T> — the general "new value, or a function from old to new" shape accepted by every set* method, mirroring React's useState setter overload (Ch 28).