Skip to content

tools: auto fix custom eslint rule for crypto-check.js #16647

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.

Sign up for GitHub

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

Closed
shobhitchittora wants to merge 7 commits into from
Closed

tools: auto fix custom eslint rule for crypto-check.js #16647

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
b35d423
tools: auto fix custom eslint rule for crypto-check.js
shobhitchittora Oct 31, 2017
803357b
tools: auto fix custom eslint rule for crypto-check.js
shobhitchittora Feb 4, 2018
6d6cdc6
tools: auto fix custom eslint rule for crypto-check.js
shobhitchittora Feb 4, 2018
1f52446
tools: auto fix custom eslint rule for crypto-check.js
shobhitchittora Feb 4, 2018
2ecf517
tools: auto fix custom eslint rule for crypto-check.js
shobhitchittora Feb 4, 2018
1018b5b
tools: auto fix custom eslint rule for crypto-check.js
shobhitchittora Feb 15, 2018
46206b7
tools: auto fix custom eslint rule for crypto-check.js
shobhitchittora Feb 17, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
tools: auto fix custom eslint rule for crypto-check.js 
Adds "missing crypto" message in tests.

Refs : #16636
  • Loading branch information
@shobhitchittora
shobhitchittora committed Feb 12, 2018
commit 1f52446e6a9a00b6f202cc8b89e5434e86520a05
10 changes: 5 additions & 5 deletions test/parallel/test-eslint-crypto-check.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ new RuleTester().run('crypto-check', rule, {
if (!common.hasCrypto) {
common.skip();
Copy link
Copy Markdown
Member

@targos targos Jan 20, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this (and other occurences below) pass the test? I think the 'missing crypto' message is missing.

Copy link
Copy Markdown
Contributor Author

@shobhitchittora shobhitchittora Feb 4, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the string 'missing crypto' in tests. But there's still something wrong. Any help?

Copy link
Copy Markdown
Contributor Author

@shobhitchittora shobhitchittora Feb 15, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done now.

}
require('crypto');
require("crypto");
`
Copy link
Copy Markdown
Member

@BridgeAR BridgeAR Feb 10, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: unnecessary change.

],
invalid: [
Expand All @@ -25,19 +25,19 @@ new RuleTester().run('crypto-check', rule, {
errors: [{ message }],
output: `
if (!common.hasCrypto) {
common.skip();
common.skip("missing crypto");
}
require('crypto');
require("crypto");
Copy link
Copy Markdown
Member

@BridgeAR BridgeAR Feb 10, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can not be the proper output because there is no common imported in the code.

`
},
{
code: 'if (common.foo) {} require("crypto")',
errors: [{ message }],
output: `
if (!common.hasCrypto) {
common.skip();
common.skip("missing crypto");
}
require('crypto');
require("crypto");
Copy link
Copy Markdown
Member

@BridgeAR BridgeAR Feb 10, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can not be the expected output because common is not imported. But not only that, the first statement if (common.foo) {} was just removed? That is definitely not right.

`
}
]
Expand Down