| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
🥇 Love this!
Sorry, something went wrong.
There was a problem hiding this comment.
Commented code
Sorry, something went wrong.
There was a problem hiding this comment.
This is really great!!
My only concern is that there might be errors that are documented, but don't exist anymore in lib/internal/errors.js (this had come up at least once or twice). I had made my own lintdoc.js to try and deal with this (I had meant to PR into nodejs/node at some point). Not a huge deal, just probably just something collaborators should keep in mind as things land.
Sorry, something went wrong.
There was a problem hiding this comment.
needs a comma after ever :)
Sorry, something went wrong.
There was a problem hiding this comment.
✂️?
Sorry, something went wrong.
There was a problem hiding this comment.
I could be missing something, but do we need to have this test file if we already have the lint rule, and it's enabled for lib/internal/errors.js? In theory the lint rule should run as part of make lint, right? 😬
Sorry, something went wrong.
There was a problem hiding this comment.
The test file tests the lint rule -- make lint runs it.
Sorry, something went wrong.
There was a problem hiding this comment.
This test file is intended to test the lint rule itself. For example, if the rule had a bug where it never reported any errors, we probably wouldn't notice it when running make lint.
Sorry, something went wrong.
There was a problem hiding this comment.
👍 sorry, my bad, I read RuleTester as running the rule.
Sorry, something went wrong.
Sorry, something went wrong.
|
@maclover7 ... regarding codes that are in errors.md that aren't used any more, let's tackle that problem separately.. perhaps by using @watilde's md lint tool once that lands. |
Sorry, something went wrong.
PR-URL: #16450 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Teddy Katz <teddy.katz@gmail.com>
PR-URL: #16450 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Teddy Katz <teddy.katz@gmail.com>
Sorry, something went wrong.
PR-URL: nodejs/node#16450 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Teddy Katz <teddy.katz@gmail.com>
PR-URL: nodejs/node#16450 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Teddy Katz <teddy.katz@gmail.com>
|
Should this be backported to v8.x-staging? If yes please follow the guide and raise a backport PR, if no let me know or add the dont-land-on label. I landed 76b8803 as it had no conflicts, so it's just fb477f3 that needs backporting. Obviously that fails linting 😁 , if someone could backport both that'd be ideal |
Sorry, something went wrong.
PR-URL: nodejs/node#16450 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Teddy Katz <teddy.katz@gmail.com>
PR-URL: nodejs/node#16450 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Teddy Katz <teddy.katz@gmail.com>
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
doc, tools