GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||
GeezerVison is showing github.com — [v20.x backport] backport: esm: require braces for modules code by GeoffreyBooth · Pull Request #50268 · nodejs/node Conversation
|
|
Review requested:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
PR-URL: nodejs#49657 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Jacob Smith <[email protected]>
fc934ad to
83e582a
Compare
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| { | ||
| files: [ | ||
| 'lib/internal/modules/**/*.js', | ||
| ], | ||
| rules: { | ||
| 'curly': 'error', | ||
| }, | ||
| }, |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Can you remove this to avoid getting error when backporting commits that landed before this rule was introduced?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
If there are commits to backport from before this rule, I highly recommend to backport them first.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I don't know if they actually are any, regardless having less strict lint rules on LTS lines seems like a good idea to me, but it's just a nit
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
So I looked into this, and the only two commits from before this rule are:
globalPreload hook (superseded by initialize) #49144, which @aduh95 requested not be backported. It also wouldn’t run afoul of this rule regardless, because it’s almost all deletions and the few additions include the newly required braces.So I think the rule is fine to backport, and I’d rather not create unnecessary divergences from main. This rule is also very easy to abide by, and the linter can fix for it automatically.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Landed in 0103979 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
PR-URL: #49657 Backport-PR-URL: #50268 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Jacob Smith <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.