vue/comment-directive ​

support comment-directives in <template>

• ⚙️ This rule is included in all of "plugin:vue/base", "plugin:vue/essential", "plugin:vue/vue3-essential", "plugin:vue/strongly-recommended", "plugin:vue/vue3-strongly-recommended", "plugin:vue/recommended" and "plugin:vue/vue3-recommended".

Sole purpose of this rule is to provide eslint-disable functionality in the <template> and in the block level. It supports usage of the following comments:

• eslint-disable
• eslint-enable
• eslint-disable-line
• eslint-disable-next-line

📖 Rule Details ​

ESLint doesn't provide any API to enhance eslint-disable functionality and ESLint rules cannot affect other rules. But ESLint provides processors API.

This rule sends all eslint-disable-like comments as errors to the post-process of the .vue file processor, then the post-process removes all vue/comment-directive errors and the reported errors in disabled areas.

The eslint-disable-like comments can be used in the <template> and in the block level.

The eslint-disable comments has no effect after one block.

The eslint-disable-like comments can include descriptions to explain why the comment is necessary. The description must occur after the directive and is separated from the directive by two or more consecutive - characters. For example:

🔧 Options ​

{
  "vue/comment-directive": ["error", {
    "reportUnusedDisableDirectives": false
  }]
}

• reportUnusedDisableDirectives ... If true, to report unused eslint-disable HTML comments. default false

{ "reportUnusedDisableDirectives": true } ​

📚 Further Reading ​

• Disabling rules with inline comments

🚀 Version ​

This rule was introduced in eslint-plugin-vue v4.1.0

🔍 Implementation ​

• Rule source
• Test source