-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Comments are outdented incorrectly in script blocks #557
Labels
bug
Something isn't working
Comments
In objects, this bug only happens on the first commented out key. Here, it will complain only about the Repro<script>
/* eslint svelte/indent: "error" */
const obj1 = {
a: '',
b: '',
// c: '',
// d: '',
// e: '',
}
</script>
I tried creating a playground link but the indent rule doesn't work at all there (I disabled all rules except svelte/indent). But if you paste my snippet into the rule's example page you can reproduce the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before You File a Bug Report Please Confirm You Have Done The Following...
What version of ESLint are you using?
8.46.0
What version of
eslint-plugin-svelte
are you using?2.32.4
What did you do?
I linted the following outdented code using the enclosed ESLint configuration.
What did you expect to happen?
I expected ESLint to indent the code correctly; in my opinion, that is:
What actually happened?
Fixing it by running
eslint --fix
changed it to the following:Link to GitHub Repo with Minimal Reproducible Example
Repository: https://github.com/garraflavatra/svelte-eslint-comment-repro.
The original code is in
original.svelte
, the expected result is inexpected.svelte
, and the actual output is inactual.svelte
. The.eslintrc.json
file contains the used (minimal) configuration.Additional comments
I tried looking for similar issues before creating this one, but found none.
Thank you for maintaining this plugin. I use it frequently, and this is the only issue I've encountered.
The text was updated successfully, but these errors were encountered: