-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to disable "inferred as global component" warning #197
Comments
Just spent a few hours trying to get rid of this warning. Would be great to be able to supress the warning. |
You can configure global components using vueconfig.json, e.g. https://github.com/znck/vue-developer-experience/blob/main/samples/feature-vue-project-configured/vueconfig.json |
I also ran into this and looked at the samples folder to find that config, I specified it to include |
Attribute completion depends on type definitions but it will support web types soon. |
How do you specify |
I created a {
"globalComponents": ["vuetify"]
} |
The component 'van-circle' is inferred as global component. It may not be available at runtime.VueDX(59002) |
Is your feature request related to a problem? Please describe.
I have a number of globally-registered components, and I do this quite on purpose. VueDX is throwing warnings because of this, and there does not appear to be a way to disable this metric. Global registration of components is not always appropriate, but it should not always result in a warning.
Describe the solution you'd like
An option to disable this rule, and documentation for how to use the option.
Describe alternatives you've considered
Registering components locally is an alternative, but is untenable due to the number of potential code changes this would require.
The text was updated successfully, but these errors were encountered: