Toma
Toma
When first rendered, the onUpdate function is called and even if the default state canSubmit is set to false, the statement (image below) is always true and sets canSubmit to...
Have you tried using the [Required] annotation at property level? It worked for me, but I use [openapi-typescript-codegen](https://github.com/ferdikoomen/openapi-typescript-codegen). 
Hey @crutchcorn is this issue still up to date? If so, I think I can try to implement a small part of it.
> I think this is a bug with our `moveValue` method. I'll investigate in a bit If it saves a little time, after some research, I wrote a test to...
I quickly passed by here and was seeing something like this, it probably doesn't work and I don't have time to test/research in depth but maybe it will help: ```typescript...
Maaaybe this? (Sorry, it's not very clean and I'm not sure at all) ```typescript import { safeParse, safeParseAsync } from 'valibot' import type { BaseIssue, BaseSchema, BaseSchemaAsync } from 'valibot'...
> I'm sorry for my slow understanding. > > The current type of `validatorAdapter`: > > ```js > export type Validator = () => { > validate(options: { > value:...
It should be ok for valibot, the PR is open, we should be able to do the same for the other validators