Dónal Murtagh

@yacosta738 I'm using the latest versions of Vuelidate/Vitest/Vue. When I initilaize Vuelidate like this, it works ```javascript import { useVuelidate } from '@vuelidate/core' export default { data() { return {...

It's possible to make the current version of the promise plugin work in an ESLint v9 flag configuration file using `@eslint/compat` by following [these instructions](https://eslint.org/blog/2024/05/eslint-compatibility-utilities/). In my case I made...

> For anyone else looking for this functionality until it is fully implemented, here is how I fixed it: > This doesn't _exactly_ replicate the mobile support in v2. Specifically,...

> While we wait patiently for this to come true, has anyone figured out a workaround to bypass the `parserOptions` errors? Yes! It's possible to make the current version work...

> Given that, should we consider moving forward with these images? I would appreciate it if someone could review/release these images. Given that Java has a 6-month release cadence, if...

I tried this out by making the following change to the Simple example on the [demo page](http://networknt.github.io/react-schema-form/) In the form definition, replace ``` "email", ``` with: ``` { "key": "email",...

@xspaniki in the options API example you're missing the import for `email` and `required`

You can validate the current model at any point by calling [$validate()](https://vuelidate-next.netlify.app/api/methods.html#validate)

As discussed in #4546, I would like the build to fail if there are any errors or warnings, but all errors and warnings should be reported.

See https://github.com/samdjstevens/java-totp/issues/53