-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
tools: capitalize sentences #24808
tools: capitalize sentences #24808
Conversation
As a note: this rule is able to autofix. |
54fd67c
to
f89cbcd
Compare
This needs some reviews. @nodejs/documentation PTAL (it is somewhat loosely related to docs). |
@nodejs/linting PTAL |
f89cbcd
to
2c65b85
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since a review was requested from me:
No objection. I'm not a fan of all the churn for something like this, but I'm also not a fan of watching nit after nit to newcomer contributors telling them to capitalize comments, so I'm good with it.
One nit on the commit message: I'd prefer if "comments" appeared somewhere in the first line of the commit message so that someone scanning commits doesn't think this is about other text.
Needs a rebase. (One test was moved from parallel to sequential.) |
I see where you're coming from. That said, I think it's important that nits like these are handled by the tooling. Ideally, IMHO, there should be no nits on the actual PR. The linting setup should be powerful enough to take care of all possible nits and more. This PR helps in that respect, I feel. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great catch.
@ryzokuken Yeah, that's what I was trying to say. I'm not a fan of Collaborators leaving nits about this sort of thing all the time. I'd prefer the tooling do it. So, despite the churn, I"m OK with this. |
This adds the `capitalized-comments` eslint rule to verify that actual sentences use capital letters as starting letters. It ignores special words and all lines below 62 characters.
31e2b32
to
26d88c8
Compare
This adds the `capitalized-comments` eslint rule to verify that actual sentences use capital letters as starting letters. It ignores special words and all lines below 62 characters. PR-URL: nodejs#24808 Reviewed-By: Sam Ruby <rubys@intertwingly.net> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Ujjwal Sharma <usharma1998@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
Landed in 1f85ea9 |
This adds the `capitalized-comments` eslint rule to verify that actual sentences use capital letters as starting letters. It ignores special words and all lines below 62 characters. PR-URL: #24808 Reviewed-By: Sam Ruby <rubys@intertwingly.net> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Ujjwal Sharma <usharma1998@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
This adds the `capitalized-comments` eslint rule to verify that actual sentences use capital letters as starting letters. It ignores special words and all lines below 62 characters. PR-URL: nodejs#24808 Reviewed-By: Sam Ruby <rubys@intertwingly.net> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Ujjwal Sharma <usharma1998@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
This adds the
capitalized-comments
eslint rule to verify thatactual sentences use capital letters as starting letters. It ignores
special words and all lines below 62 characters. That way it will
mainly detect sentences. This way the code changes are kept low.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes