validateOnAdd fields or nested fields

[jcheroske]

This library is incredible! Thank you for all your hard work.

I'm seeing a behavior that's confusing me, and I just wanted to make sure it was by-design.

When I have validateOnInit: true and showErrorsOnInit: false, the form starts with the following properties set:

{
  isValid: false,
  hasError: true,
  error: null
}

That all looks correct to me.

If I then add an element to a nested field array, and look at the initial state of one of the newly created fields, I see its initial state as:

{
  isValid: true,
  hasError: false,
  error: null
}

It seems like, when adding a nested field, it's not being validated upon creation. In other words, adding a field dynamically doesn't seem to respect the validateOnInit flag. Is this correct? Is there a way to have newly added nested fields undergo an initial validation?

[jcheroske]

After thinking about this some more, I can see that I was misunderstanding the validateOnInit flag. I'm curious though about my question at the end of my previous post. Does it make sense to add a validateOnAdd flag that causes newly created fields to be validated immediately after onAdd is called?

[foxhound87]

This is a good question, and can be a good enhancement to have.

I will think about how implement it for the next releases.

Thank You for the contribution.

[foxhound87]

Sorrry, not going to implement this validateOnInit "per field" option because the validation validates all the form (with nested fields).

To validate after adding a field just do:

fieldset.add().validate();