-
-
Notifications
You must be signed in to change notification settings - Fork 381
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
Add import-style
rule
#789
Conversation
eed1682
to
899c96f
Compare
Are we going to allow check `./util'? |
I would prefer not to. |
9e2dc29
to
2a02047
Compare
I stumbled across this while looking for a way to enforce the use of Do y'all think this would be something appropriate to add to this |
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.
I'll take a deep look ASAP.
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.
Looks great ,
- I didn't see
import chalk, {red } from
test - We agree to check
export from
in previous PR
@fisker I added The original motivation for this rule (as far as I understand) was to force the named import of unrelated functions and default or namespace import of related functions. export {promisify, callbackify} from 'util'; I think the above code should not be reported. @sindresorhus, hope this decision is fine by you. |
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.
All good, 2 notes:
-
I suggest apply this, but it's only a style issue
Addimport-style
rule #789 (comment) -
Add a test about this, I can accept any result about it
Addimport-style
rule #789 (comment)
I addressed the remaining review comments. |
Great work on this, @futpib 👍🏻 |
fixes #211
IssueHunt Summary
Referenced issues
This pull request has been submitted to:
util
Node.js core module directly