Are you submitting a bug report or a feature request?
bug report
What is the current behavior?
The current behavior is that when there are existing rows in initialValues the FieldArrays validate function when returning [undefined] impacts the field level validation. Interestingly, this does not affect any new rows.
The field level validation checks if the value === bad. You will notice that typing bad in the first row does not result in an error but in any new rows it does work. The FieldArray's validate is simply: () => [undefined]
What is the expected behavior?
FieldArray validation should not impact Field level validation. This worked in:
Are you submitting a bug report or a feature request?
bug report
What is the current behavior?
The current behavior is that when there are existing rows in
initialValues
theFieldArray
svalidate
function when returning[undefined]
impacts the field level validation. Interestingly, this does not affect any new rows.See: https://codesandbox.io/s/react-final-form-field-arrays-forked-bqtle?file=/index.js
The field level validation checks if the value ===
bad
. You will notice that typingbad
in the first row does not result in an error but in any new rows it does work. TheFieldArray
'svalidate
is simply:() => [undefined]
What is the expected behavior?
FieldArray validation should not impact Field level validation. This worked in:
but fails in:
Sandbox Link
https://codesandbox.io/s/react-final-form-field-arrays-forked-bqtle?file=/index.js
What's your environment?
This worked in:
but fails in:
Other information