[capitalized-comments] Should not autofix multiline when `ignoreConsecutiveComments`
See original GitHub issueTell us about your environment
- ESLint Version: 3.12.2
- Node Version: 6.9.1
- npm Version: Yarn 0.18.1
What parser (default, Babel-ESLint, etc.) are you using? babel-eslint
Please show your full configuration:
rules: {
'capitalized-comments': [2, 'always', {'ignoreConsecutiveComments': true}],
}
What did you do? Please include the actual source code causing the issue.
Ran eslint --fix
against code like:
// this is a multi-line comment that does not start with a capital letter, and maybe
// describes some variables like:
// foo - this is a thing
// fooFighter - it fights the foo
What did you expect to happen?
// This is a multi-line comment that does not start with a capital letter, and maybe
// describes some variables like:
// foo - this is a thing
// fooFighter - it fights the foo
What actually happened? Please include the actual, raw output from ESLint.
// This is a multi-line comment that does not start with a capital letter, and maybe
// Describes some variables like:
// Foo - this is a thing
// FooFighter - it fights the foo
I’m proposing that when ignoreConsecutiveComments
is true
, the rule should not auto-capitalize lines other than the first line.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
capitalized-comments - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >React typescript: eslint max-length autofix does not work
I am trying setup React typescript's eslint setup where code's max lenght is 80, if the code is more than 80 then it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This was fixed by #7835, I just forgot to add the “(fixes #7831)” to the commit message. Oops 😞
I’d like to fix this, if possible. Hoping to get to it this weekend (certainly long before the next minor release next Friday).