-
-
Notifications
You must be signed in to change notification settings - Fork 679
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
Issues with vue/no-unused-components #556
Labels
Comments
Hey @sqal! Thanks for posting this issue.
|
@michalsnik I think this rule should automatically exclude the case that |
@michalsnik I have a third issue with <template>
<svg xmlns="http://www.w3.org/2000/svg" width="100%">
<g v-for="(step, stepKey) of steps" :key="stepKey">
<g v-for="(job, jobKey) of step" :key="jobKey">
<svg-pipeline-job :step="step" :job="job" />
</g>
</g>
</svg>
</template>
<script>
import SvgPipelineJob from './SVGPipelineJob'
export default {
name: 'svg-pipeline',
components: {
/* eslint-disable vue/no-unused-components */
SvgPipelineJob
}
}
</script> Same version used. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tell us about your environment
Please show your full configuration:
What did you do? Please include the actual source code causing the issue.
Issue 1
Erors:
Issue 2
Errors:
What did you expect to happen?
Regarding issue nr. 1.
As you can see, in the template I write components names in PascalCase because both header and footer are reserved html names. In this case I expect the plugin can detect whether component name is written in PascalCase or kebab-case.
Regarding issue nr. 2.
This is probably a very common case when someone uses dynamic component tag and uses computed property to switch between some components. In this case I think it would be great if I could somehow tell the plugin to ignore the components that are registered via special
<component />
tag.The text was updated successfully, but these errors were encountered: