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
Create script for checks (prettier, lint, flow) in CI #93
Conversation
Deploy preview ready! Built with commit 5a96b1d |
Some thoughts! 😄
|
@bvaughn - yeah was a bit unsure about what to name it! I was wondering why the linter didn’t pick up stuff like that too! Thought there may have been some reason why you configured it that way. 😆 Will check it out later on! |
Nope. I was trying for a minimal linter config and didn't test it thoroughly enough at the time. |
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.
This looks great! Catches a lot of small lint errors that have slipped through too 😄
Looks like we may have to do something special for certain Flow types, eg:
/Users/bvaughn/Documents/git/reactjs.org/src/theme.js
48:13 error '$Keys' is not defined no-undef
But we can iterate on things like this and not hook the new Yarn task into CI until they've all been fixed.
This intends to fix #67.
check-all:verbose
script, which is similar tocheck-all
, however lists errors out on prettier if the files are different from the prettier formatting.prettier:diff
script, which checks for a difference between the prettified files, and source files.Yay or nay?