Andrew Walker
Andrew Walker
Those are the 3 options that came to my mind too. ##### 1. Run the same tests against both Vue 2 and Vue 3 with vue-test-utils and vue-test-utils-next respectively -...
I ran the migration helper for src/ and examples / - no obsolete syntax was detected. For test/, all I got was: ``` 1. Replace "src/*.{js,vue}" with "src/:.{js,vue}+" Line 21:...
I've had a couple of hours to look into this this evening. I've opened up a very, very early stages PR, but I don't necessarily expect it to be the...
Hi, @sudip571 - Vue 3 is not yet supported by vue-formulate. It's on the future roadmap, but it will not work right now.
Hey @justin-schroeder, hot on the heels of the full Vue 3 release announcement - have you thought any more about whether to have a separate `-next` package or not?
Hmm, I can see how that could be tricky. When you talk about tree shaking, do you mean when you're bundling with rollup to deploy vue-formulate to npm? I know...
Are you using Vite v2? I haven't added support for that yet. You might want to check out https://github.com/brattonross/vite-plugin-voie as that got a lot more traction than this library.
I haven't done much with i18n before. Is there an established pattern for how these page prefixes are usually done with vue-i18n? If you point me to an example set...
If you use the following structure: ``` - pages/ - _locale/ - your-first-page - your-second-page - _locale.vue - *.vue ``` Then in `_locale.vue`: ```html import { Trans } from '../plugins/Translation'...
@lewebsimple did this work in the end?