Oleksii Shaposhnikov

> there is a third parameter of useForm,not sure if it fits your needs  Thanks, will check that

Hi everyone. I also have this issue only in prod mode. A temporary workaround: remove a `key` attribute from your `v-for`. The error will still be in the console, but...

> If anyone is still dealing with this. We worked around the error by replacing most of our `v-if` to `v-show`. Nice 😄 😄 😄

@mijreed you can use it like ``` import { defineComponent, onMounted } from "vue"; import ApexChart from "apexcharts"; export default defineComponent({ setup() { let chartInstance; const options = { colors:...

Hey guys, any updates on that? Those warnings are quite annoying. Here is a workaround: ```ts it ('...' => { const wrapper = shallowMount(Component, { global: { stubs: { 'custom-element':...

Can you provide an example of the "in-DOM" teamplate? And if possible, can you also add a docs link to a section of in-DOM templates?

Thanks, I understood. But what about your general recommendation to use kebab case everywhere in templates (because it is more natural for HTML) and camel case in JS code?

@matt-way were you able to check the issues above? It will be great if you respond 🙏🏻

Confirming this issue on my side as well 🙏🏻

I am having the same issue