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
[multline-comment-style] fix breaks code #12785
Comments
Hello, I'm not an eslint member. But, In my opinion, it looks like a bug. reproduced- demo
after fix. -> /* eslint multiline-comment-style: ["error"] */
/*
*// a line comment
*some.code();
*/ |
hi, thanks! labelled accepted, based on the repro-demo. |
I'd be interested in jumping on this one if there aren't any other takers. |
@jpramassini Please feel free! Let us know if you have any questions. |
@jpramassini Still working on this? |
Hey Karthik, sorry for the delay on this. I'm planning on knocking this out this weekend. |
@karthikkp I got the flu so I might be slower in getting to this than I thought. If you want to take a crack at it, go for it. |
@jpramassini Thank you. I am taking up this issue |
…nt#12785) (eslint#12823) * Fix: multiline-comment-style rule missed an extra space after * (fixes eslint#12785) * logic changed to handled only the edge case * test case added for the edge case * checks full offset and apply space after * only if there already isn't white space after it. * addeed new test case
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using?
babel-eslint@10.0.3
Please show your full configuration:
Configuration
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
When autofixing the following code it resulted in non-parseable js code. This is a minimal reproducible example.
What did you expect to happen?
I expect it to not yield non-parseable code.
What actually happened? Please include the actual, raw output from ESLint.
It yielded non-parseable code
The text was updated successfully, but these errors were encountered: