You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// NOTE this rule only supported in SFC, Users of the unplugin-vue-define-options should disable that rule: https://github.com/vuejs/eslint-plugin-vue/issues/1886
150
-
// 'vue/no-duplicate-attr-inheritance': 'error',
162
+
'vue/no-duplicate-attr-inheritance': 'error',
151
163
'vue/no-empty-component-block': 'error',
152
164
'vue/no-multiple-objects-in-class': 'error',
153
165
'vue/no-reserved-component-names': 'error',
@@ -191,9 +203,9 @@ module.exports = {
191
203
message: 'Use \'@images\' path alias for image imports',
192
204
},
193
205
{
194
-
regex: '@/styles',
206
+
regex: '@/assets/styles',
195
207
replacement: '@styles',
196
-
message: 'Use \'@styles\' path alias for importing styles from \'src/styles\'',
208
+
message: 'Use \'@styles\' path alias for importing styles from \'src/assets/styles\'',
Since TypeScript cannot handle type information for `.vue` imports, they are shimmed to be a generic Vue component type by default. In most cases this is fine if you don't really care about component prop types outside of templates.
12
12
13
-
However, if you wish to get actual prop types in `.vue` imports (for example to get props validation when using manual `h(...)` calls), you can run `Volar: Switch TS Plugin on/off` from VSCode command palette.
13
+
However, if you wish to get actual prop types in `.vue` imports (for example to get props validation when using manual `h(...)` calls), you can run `Volar: Switch TS Plugin on/off` from VS Code command palette.
0 commit comments