Jacek Karczmarczyk

> Vue.config.ignoredElements = [/^ui-/]; That imho is not a good option name, should be more self-explanatory. How about `.native` modifier? `v-model="foo"` would use `$event` as a value, `v-model.native="foo"` would use...

> As for how to do it in 4.1.0 or newer, I endorse using the FieldsInterface (can be fetched from the Uuid instance) Can you elaborate? `FieldsInterface` has only `getBytes()`...

Why is even `UuidV1::fromString('...')` returning anything if the argument is not a valid UUID1? Shouldn't it throw?

Is 5.0 coming soon?

> If you see anything else to bring up before the v7 release, now is the time :) Is there a migration guide to 7.0 that could be checked before...

I've tried the solution, my config is: ```js module.exports = { extends: ['jkarczm/vuetify'], parser: 'vue-eslint-parser', parserOptions: { parser: { ts: '@typescript-eslint/parser', '': 'espree', }, project: 'tsconfig.json', } } ``` First...

Thanks, but that doesn't seem to work, not only it didn't solve the problem with unrecognized `defineProps` but also added problem with recognizing `.vue` files:  and with JSX syntax:...

> `yarn add --dev @vue/runtime-dom` Thank you, that was it! I have `lang="ts"` in all components so no need for other steps, also seems that `/// ` is not necessary...

~~hm what is https://github.com/johnsoncodehk/volar then?~~ nvm, I see now still i think that putting information about dependency in the `IDE` section is misleading, writing about Vetur, Volar and VS Code...

Thanks for the solution, wouldn't it be a breaking change though? I mean technically it isn't, as prior to 3.x/2.7 there was no `ref()` and `watch()`, but what is the...