-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
test(prettier): add scripts/prettier-test.sh #384
Conversation
Here test failed because @char0n : what do you think ? |
It'd be better if it only check files that differ from |
I think CI should never fail on master, so a PR isn't a good PR if build fails. |
move prettier from `lint` to `lint:fix` npm script, run `prettier-test.sh` in `lint` Ref #379
65243a9
to
e7d812c
Compare
To simplify things, we could run Prettier from within Eslint, one step less to worry about: https://prettier.io/docs/en/eslint.html |
@@ -62,7 +62,8 @@ | |||
}, | |||
"betterScripts": { | |||
"docs": "jsdoc -c jsdoc.json && node ./scripts/jsdoc-inject-dist.js", | |||
"lint": "prettier test/**.js src/**.js --write && eslint ./ && tslint -c tslint.json src/index.d.ts", | |||
"lint": "./scripts/prettier-test.sh && eslint ./ && tslint -c tslint.json src/index.d.ts", | |||
"lint:fix": "prettier test/**.js src/**.js --write", |
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.
lint:fix
should probably also run eslint --fix
after prettier... Either directly, or by using prettier-eslint
Closing until #387 is resolved. |
lint
tolint:fix
npm scriptprettier-test.sh
inlint
npm scriptRef #379, #336