-
-
Notifications
You must be signed in to change notification settings - Fork 383
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
Run recommended config against source code #387
Conversation
/cc @sindresorhus what do you think? |
Makes sense to me. You need to add |
Just a idea, maybe a better way, will do it later |
… into run-on-self
This PR is almost done. Some source code not following recommended configs, most of them are fixed, some questions:
/cc @sindresorhus |
Can you fix the merge conflict? |
# Conflicts: # rules/prefer-dataset.js
local test passed |
@futpib any idea why CI fails? |
04e599a
to
a3ae40e
Compare
# Conflicts: # rules/no-for-loop.js # rules/no-process-exit.js # rules/prefer-exponentiation-operator.js # rules/prefer-reflect-apply.js # rules/prefer-spread.js
How the same code success on my CI? https://travis-ci.com/fisker/eslint-plugin-unicorn/builds/131622273 |
cache: | ||
npm: false |
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.
CI finally passed, should I keep 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.
Sure, for now.
Shouldn't we run recommended configs on our own repo? And our own source code should follow recommended rules.
This is a prototype, maybe move to integration test