Flo Edelmann
Flo Edelmann
I think that should be a separate rule (`vue/template-class-pattern` or similar). But if you choose to check the `class` attribute in `vue/template-attribute-value-pattern`, why should it not work?
I think in this case, disabling the `vue/dot-notation` for your project is the best option. I don't think there is a way for us to guess that 1. the project...
> a bridge for any core eslint rule We already have that: https://github.com/vuejs/eslint-plugin-vue/blob/d6f0337d88ce39214f4bf2853a5cdc26e2c30e32/lib/utils/index.js#L375
I don't know. @ota-meshi maybe you can help here?
Should this maybe also report setting of nested `ref`s? Or is reactivity working as expected in this case? ```ts const myRef = ref({ nested: 'foo' }); myRef.value = { nested:...
Thanks for checking. Then I'd suggest rule name `vue/no-deep-mutating-computed-ref`.
A PR would certainly be appreciated! I like `shallowOnly` most. Another suggestion: `ignoreDeepMutations` (`ignore` would be consistent with other rule options).
I think there is nothing we can do about this in `eslint-plugin-vue`, as this error is caused by `eslint-plugin-import` and Vue core. @ota-meshi @mysticatea Maybe [`vue-eslint-parser`](https://github.com/vuejs/vue-eslint-parser) could do something to...
Why did you close this issue? I think it's still a valid request. * ``, `` and `` are reported --- * `` is not reported * `` and ``...
I guess you are referring to https://vuejs.org/guide/components/events.html#usage-with-v-model? `onUpdate:data` should be an event, not a prop.