-
-
Notifications
You must be signed in to change notification settings - Fork 481
Issues: final-form/react-final-form
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Not possible to set numeric keys, even with multiple numbers like "5.1.1", on an object
#1042
opened Jul 31, 2024 by
BennyAlex
[Question] Is it safe to use noValidate flag on form and to prevent default native validation messages
#1041
opened Jul 16, 2024 by
amBunkowski
Form not dirty after removing items from FieldArray using final-form-arrays
#1038
opened Oct 23, 2023 by
outofthisworld
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
opened Sep 25, 2023 by
tulsiempyreal
[Feature Request] Add new prop to specify changes to specific form fields
#1021
opened Feb 7, 2023 by
jatin33
Ran into "is dirty" validation issues when state was used to autofill a form's input field.
#1020
opened Jan 23, 2023 by
ShawnCentra
Documentation for defaultValue of FieldProps is not matching implementation
#1015
opened Dec 8, 2022 by
mauron85
Previous Next
ProTip!
no:milestone will show everything without a milestone.