chore: disable multiword-rule

[manniL]

Not ideal for page components :(

Resolves #192
Better would be disabling it for the pages folder only I'd say 😋

[danielroe]

Thanks for this! Could we implement via overrides instead (e.g. for **/pages/**), as you've linked to this?

[iamarpitpatidar]

yeah, I think is better than just disabling it. as @danielroe said.

  rules: {
    'vue/multi-word-component-names': 'off',
  },
  overrides: [
    {
      files: ['components/*.{js,ts,vue}'],
      rules: {
        'vue/multi-word-component-names': 'error',
      }
    }
  ]

[manniL]

yeah, I think is better than just disabling it. as @danielroe said.

  rules: {
    'vue/multi-word-component-names': 'off',
  },
  overrides: [
    {
      files: ['components/*.{js,ts,vue}'],
      rules: {
        'vue/multi-word-component-names': 'error',
      }
    }
  ]

I'd probably do it the other way around, given that components could live in many folders but page components usually only in pages and layouts.

[iamarpitpatidar]

okay yeah that's smart..

[iamarpitpatidar]

@manniL can you check why test is failing tho ?

[KareemDa]

when this feature will be released?

installing latest version: 8.0.0 is still giving the same error

[rchl]

It doesn't handle the case when page components are in test/fixture/... for example.
Also why does it apply to .js and .ts extensions? I would think that it should only apply to .vue?

[pi0]

@rchl I suppose .js would be mostly useful for components with render function with // @vue/component however didn't try. It also makes sense to ignore **/pages/, project in subdir. Do you mind to check if **/pages also handles top level pages and make a PR?

[0x3333]

In my case, I use an 'src' folder for all my components, assets, pages, etc. The lint kicks-in in this case.