@quero/eslint-plugin-vue
This project is for rules that we decided to implement ourselves.
Content:
Rules
Legend:
| icon | meaning |
|---|---|
| Fixable | |
|
|
Partially fixable |
template-kebab-name-for-unregistered-components 🔧 *
Enforce the use of kebab-case for naming global components in <template>.
This ensures that we have a clear distinction between components that are declared locally vs components that we have to search the project for.
This rule is fixable, but only if the component don't have any extend declaration, because if thats the case, we cannot see which components are being loaded or not.
<template>
<div>
<!-- BAD -->
<GlobalComponent></GlobalComponent>
<local-component></local-component>
<!-- GOOD -->
<global-component></global-component>
<LocalComponent></LocalComponent>
</div>
</template>
<script>
const LocalComponent = {
render(h) {
return h('div');
},
};
export default {
components: {
LocalComponent,
},
}
</script>
deprecate-components-in-favor-of
A nice reminder on the lint that you shouldn't use this component, use the other one instead
It's super recommended running this rule as warn, otherwise, what would be
the point of using this rule at all if the rule will fail everything? Just
delete the unused component on this case.
Default
{
"rules": {
"@quero/vue/deprecate-components-in-favor-of": ["warn", { }]
}
}With the default configuration everything will pass. But if a deprecate
option is provided like the example bellow; every component named
"deprecate-component-name" will trigger a warn to be substituted by
"substituted-component"
{
"rules": {
"@quero/vue/deprecate-components-in-favor-of": ["warn", {
"deprecate": {
"deprecated-component-name": "substituted-component",
"AnotherExample": "substituted-component"
}
}]
}
}<template>
<div>
<!-- BAD -->
<DeprecatedComponentName></GlobalComponeDeprecatedComponentName>
<deprecated-component-name></deprecated-component-name>
<deprecated-component-name />
<AnotherExample />
<another-example />
<!-- GOOD -->
<!-- literally anything else -->
</div>
</template>
<script>
const LocalComponent = {
render(h) {
return h('div');
},
};
export default {
components: {
LocalComponent,
},
}
</script>Developing
For constructing and testing the rule, we can use a tool called AST explorer. The AST stats for an abstract syntax tree which is a representation of the source code in a programming language.
When accessing the AST explorer, remember to set the transformer to ESLint v4 (and the parser to eslint-babel, but this should be set automatically once you choose ESLint v4). When this is done, you should see 4 windows in the explorer:
+-[top left]---------------+-[top right]--------------+
| Is used to write a | Is the explorer of the |
| source code. | source code. On hover |
| | you should see the |
| | highlighted parts in |
| | your code. |
+--------------------------+--------------------------+
| Is the rule. | Is the output after the |
| | rule, that runs against |
| | the code. |
| | |
+-[bottom left]------------+-[bottom right]-----------+
The rule window, should export a function that is the rule you are developing.
For more information on how to create your first rule, see How To Write Your First ESLint Plugin.
More resources that are an interesting read before/while: