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

Fails to lint vue with a style tag that contains 4 tab spacing #557

Open
7 tasks done
yuvalkarif opened this issue Jul 20, 2024 · 0 comments
Open
7 tasks done

Fails to lint vue with a style tag that contains 4 tab spacing #557

yuvalkarif opened this issue Jul 20, 2024 · 0 comments

Comments

@yuvalkarif
Copy link

yuvalkarif commented Jul 20, 2024

Describe the bug

When using formatters: true in a vue file that has a style tag, that for some reason had a 4 tab indent spacing, eslint throws and fails.
This issue seems to be somewhat related, but I'm not sure if we should cover this case in the tests / if the fix should be in this repo or not.

<style>
 .bd-examples>[class^="col-"]  {
  	padding-right: .75rem;
  						padding-left: .75rem;
  
  }
</style>

image

Reproduction

https://github.com/yuvalkarif/eslint-config/tree/yuvalkarif/vue-style-tab-fails

System Info

System:
    OS: Linux 5.15 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor
    Memory: 4.30 GB / 7.73 GB
    Container: Yes
    Shell: 5.8.1 - /usr/bin/zsh
  Binaries:
    Node: 20.12.0 - ~/.nvm/versions/node/v20.12.0/bin/node
    npm: 10.8.1 - ~/.nvm/versions/node/v20.12.0/bin/npm
    pnpm: 9.3.0 - ~/projects/eslint-plugin-format/node_modules/.bin/pnpm

Used Package Manager

pnpm

Validations

  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • The provided reproduction is a minimal reproducible of the bug.

Contributions

  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant