Abdelrahman Awad

Similar to https://github.com/logaretm/vee-validate/issues/4142 Still need to find a way to do this seamlessly otherwise it will be confusing.

That is reasonable, I will try to figure something out.

We currently walk the tree of validations applied on each schema provider, this won't work for dynamic schemas. So a different approach might be needed here. I will mark this...

This is partially implemented if you use `refs` instead to build your schemas in c4415f8a5fdec3dcb377c4e1a67399a089ee9d4a. Or `computed` which is a valid alternative to using the `lazy` APIs. Still there is...

I don't think this is intended, but not sure if it is a bug either, I never thought about this case nor it is in any of the tests we...

Thanks, I will take a look when I can (around the weekend)

Hey @zaalbarxx, Unfortunately I have not had the time to check this out yet. This is a significant feature work and I would like to make sure we aggressively scope...

Dropped them during the upgrade to v4 and never implemented them since, will consider adding them in the next minor release.

This came up before, but mixing field and form validation levels are not something I like to support or encourage since it means: - We need to handle merging the...

@mohanadkandil Be my guest, basically, we need to allow both bracket and dot syntax to reference arrays.