-
-
Notifications
You must be signed in to change notification settings - Fork 681
Rule proposal: no-reserved-component-names #486
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
Comments
This makes sense, but I think it should be focused on avoiding reserved names in component definitions, e.g. |
Some examples of code it should catch: Vue.component('font-face', {}) const name = 'font-face'
Vue.component(name, {}) // filename: font-face.vue
export default {
name: 'font-face'
} // filename: font-face.vue
module.exports = {
name: 'font-face'
} |
I think we should also warn about:
This returns same warning in Vue app, as former examples. @chrisvfritz @shadskii |
I've added warnings for locally registered components in #757. Thank you for the suggestion! |
see https://stackoverflow.com/a/22545622/248058
Those names should produce an error:
The text was updated successfully, but these errors were encountered: