Skip to content
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

fix: fixed the errors of eslint #1675

Merged
merged 2 commits into from
Jan 22, 2022
Merged

Conversation

yunnysunny
Copy link
Contributor

Superagent has three eslint configuration files. The .lib.eslintrc to valid the files under the directory of lib , the .dist.eslintrc to valid the files under the direcotry of dist, the property of xo of package.json to valid all the project's file.

For the issue of xojs/xo#598 from xo ,we can not disable the rule for low version node check, such as the rule node/no-unsupported-features/node-builtins. So I just switch to use the native eslint, and add a new configuration file, named .eslintrc. This will also benefit for the vscode, when use the file .eslintrc , vscode can use the rules from it.

For current project not install the eslint plugin of eslint-plugin-unicorn in package.json. So I have not set it as an extendtion to .eslintrc. Someone can install it manual and use the rules from it after the pull request is merged.

@@ -55,7 +55,7 @@ describe('request', function () {

try {
var file = new File([''], 'image.jpg', { type: 'image/jpeg' });
// eslint-disable-next-line unicorn/prefer-optional-catch-binding
////eslint-disable-next-line unicorn/prefer-optional-catch-binding
Copy link
Collaborator

Choose a reason for hiding this comment

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

Just remove this line altogether?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Has removed it

Copy link
Collaborator

@niftylettuce niftylettuce left a comment

Choose a reason for hiding this comment

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants