Skip to content
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

Handle component multi-word with Nuxt components prefix #261

Closed
Atinux opened this issue Jan 10, 2023 — with Volta.net · 3 comments
Closed

Handle component multi-word with Nuxt components prefix #261

Atinux opened this issue Jan 10, 2023 — with Volta.net · 3 comments
Labels
enhancement New feature or request

Comments

Copy link
Member

Atinux commented Jan 10, 2023

We should not have those warning with Nuxt since we do prefix by default:
CleanShot 2023-01-10 at 17.04.15@2x.png

You can test easily on https://github.com/nuxtlabs/nuxtlabs.com/tree/eslint-config @danielroe with running npm run lint

@MuhammadM1998
Copy link

I stumbled on this today. I'm setting a custom prefix in nuxt.config

export default defineNuxtConfig({
  modules: ['@nuxt/eslint'],
  components: [{ path: '/components', prefix: 'CB' }],
})

With the following file tree

| components
  | --- Logo.vue

I get the following error

D:\my-base-layer\components\Logo.vue
  1:1  error  Component name "Logo" should always be multi-word  vue/multi-word-component-names

Removing the custom prefix from the config and moving all the components to components/CB folder yields the same error

@antfu
Copy link
Member

antfu commented May 2, 2024

The issue should be solved with the 0.3 rewrite and no longer relevant.

@MuhammadM1998 Please create another issue with minimal reproduction. Thanks.

@antfu antfu closed this as completed May 2, 2024
@MuhammadM1998
Copy link

@antfu I've created a reproduction and an issue #419

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants