Abdelrahman Awad

Not sure what is going on here. Perhaps the server is wrapping the response object? Can you point me to the API if it is public?

Sorry for the delay, just got around to this. The [plugin doesn't expose](https://github.com/logaretm/villus/blob/main/packages/villus/src/cache.ts#L79)`setCacheResult`, only the `clear` method. But I guess we could expose it, will try to tackle it this...

Hello, it is the other way around. Sorry, I didn't find the time to work on it, busy with vee-validate at the moment. It is as simple as you suggested....

> Is there anything that I can do to help move this forward? Feel free to PR it if you have the time, I know it's a 1 liner but...

It's unlikely I will be maintaining 3rd party library bindings myself. But I would love to help if anyone wants to create one.

@hanzelkatomas is correct, vee-validate assumes they are all part of the same group so they would be represented as an array and `length` is the correct way to force certain...

You need to use [`toTypedSchema`](https://vee-validate.logaretm.com/v4/guide/composition-api/typed-schema/#yup-default-values) for the `.default` to take effect. You need to install `@vee-validate/yup` which is showing in nuxt warning console. ```ts const formSchema = toTypedSchema( // Your...

Noted for v5, as it is related to https://github.com/logaretm/vee-validate/issues/4630 Normalizing the validation triggers and error messages display to userland would make it easier to apply this change. As of now,...

I don't think this was suggested in the docs anywhere. `Form` component does not emit any event besides the `submit` event and `invalid-submit`. If you want to be notified of...

Typed schemas doesn't support field-level schemas at the moment. It should work with form-level schemas.