Given isValid.elements is implemented in validation.ts, do we still need it here? (same for any other field type)

I added this because, without it, the validation is run whenever the elements are present. Including when it is okay to add new elements

Is this code ever executed? I'd think we can remove it because it's covered by the control here, and so it never checks the custom validation here (that will run the same check again for elements).

There are a few levels to validation:

• Control-level: the array control handles element validation, providing the corresponding message if it's invalid.
• Form-level, via the isItemValid utility: this handles element validation (this is for form-level).

By introducing isValid.elements I understand that we can:

• remove the existing checks in all field types (previously bundled as part of isValid.custom)
• make sure every control handles isValid.elements properly (done for the array control)
• make sure isItemValid also handles it (done)

Does this make sense, or am I missing any context here?

After seeing it closely, I agree that this part was inadvertently executed (as I recorded in the video), but it should be removed altogether f2e301d

Now that it is removed, and regarding this part:

make sure every control handles isValid.elements properly (done for the array control)

I only see the select control that might benefit from such validation. Should I implement it there, too?