initialValues along with useField yields undefined initially

I must say that was rather a painful moment before I’ve debugged what’s happening there. Apparently, the initialValues are ignored until the field is registered. I am not sure if it’s an attempt for some optimization or a limitation of architecture, but I think it’s wrong.

<Form initialValues={{ listOfSomething: [] }}><FormSection /></Form>

const FormSection = () => {
  const { fieldState } = useField('listOfSomething')
  // fieldState is undefined on initial render
}

One can argue that I should be checking for value there to increase encapsulation and not rely on that initialValues will be set. That’s a fair assumption, but it doesn’t feel right to be forced to do it every time.

[joepuzzo]

I think i have solved this!

[joepuzzo]

So here is the issue with this. I designed informed with a key point in mind. And that is all fields should be independent of one another and independent of a Form if they want to be. BUT if they were within a form, then they would register themselves witht that form. Because of this however, until the field registers itself with the form then the useField wont have the registered data, i have been thinking a lot about this and may be able to do some playing to get registration to happen on initial render tho