We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Checklist
Tell us about your environment
Please show your full configuration:
/* eslint-env node */ module.exports = { root: true, extends: [ "plugin:vue/vue3-recommended", "eslint:recommended" ], env: { "vue/setup-compiler-macros": true, }, };
What did you do?
<template> <div style="color: red;"> <slot camelCase withValue="foo" :withBind="1" fooBar-BAZ_QuX /> </div> </template>
What did you expect to happen? I expect warnings like this to appear:
Attribute 'withVariableBind' must be hyphenated. eslint(vue/attribute-hyphenation)
What actually happened?
Nothing happens.
Repository to reproduce this issue
https://github.com/yusufkandemir/eslint-plugin-vue-slot-issue
Might be related to 602d80f
<slot> is a native HTML element(related to Web Components), but the rule should also run on that, just like it used to do before.
<slot>
The text was updated successfully, but these errors were encountered:
Fix vuejs#1808: Lint slots in attribute-hyphenation
3980a55
Fix #1808: Lint slots in attribute-hyphenation (#1826)
f59de96
* Fix #1808: Lint slots in attribute-hyphenation * remove includeSlots option * remove stray linting
Successfully merging a pull request may close this issue.
Checklist
Tell us about your environment
Please show your full configuration:
What did you do?
What did you expect to happen?
I expect warnings like this to appear:
What actually happened?
Nothing happens.
Repository to reproduce this issue
https://github.com/yusufkandemir/eslint-plugin-vue-slot-issue
Might be related to 602d80f
<slot>
is a native HTML element(related to Web Components), but the rule should also run on that, just like it used to do before.The text was updated successfully, but these errors were encountered: