Issues

useField v7.0.1 overwrites form values set via change() for previously unregistered field paths

#1095

· StevenHensgen opened

on Jul 8, 2026

`useField` returns an empty string on the first render for a newly added array item

#1093

· romancavry opened

on Jun 30, 2026

Update final-form dependency

#1091

· antonkamardin opened

on May 25, 2026

Ref broken on custom component

#1082

· barettjfed opened

on Mar 12, 2026

Form not calling `formatOnBlur` before validating when submitted using Enter key

#1044

· anmol-kansal-ds opened

on Jan 7, 2025

Not possible to set numeric keys, even with multiple numbers like "5.1.1", on an object

#1042

· BennyAlex opened

on Jul 31, 2024

[Question] Is it safe to use noValidate flag on form and to prevent default native validation messages

#1041

· amBunkowski opened

on Jul 16, 2024

Field-Level validation for root and nested fields

#1039

· alena-apanovich opened

on Feb 2, 2024

Form not dirty after removing items from FieldArray using final-form-arrays

#1038

· outofthisworld opened

on Oct 23, 2023

I believe defaultValue should be the DEFAULT. That means, if NO initialValue was passed in, the defaultValue would be used. If there is an initialValue, it should override the defaultValue. One work around is using an OR in initialValues and skip using defaultValue all together like so:

#1037

· tulsiempyreal opened

on Sep 25, 2023

Submitting Images in React Final Form

#1036

· HarshArora-1205 opened

on Aug 11, 2023

useField does not rerender component, when its props change

#1035

· CUzkov opened

on Aug 4, 2023

Navigation Menu

Uh oh!

Uh oh!

All issues

useField v7.0.1 overwrites form values set via change() for previously unregistered field paths

`useField` returns an empty string on the first render for a newly added array item

Update final-form dependency

Ref broken on custom component

Form not calling `formatOnBlur` before validating when submitted using Enter key

Not possible to set numeric keys, even with multiple numbers like "5.1.1", on an object

[Question] Is it safe to use noValidate flag on form and to prevent default native validation messages

Field-Level validation for root and nested fields

Form not dirty after removing items from FieldArray using final-form-arrays

I believe defaultValue should be the DEFAULT. That means, if NO initialValue was passed in, the defaultValue would be used. If there is an initialValue, it should override the defaultValue. One work around is using an OR in initialValues and skip using defaultValue all together like so:

Submitting Images in React Final Form

useField does not rerender component, when its props change

Uh oh!

Uh oh!

Search results