-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use the same eslint config as API #5
Conversation
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.
Fix also runs formatting? Or just fixes warnings?
Can we run the formatter in CI and then run a git command to fail the workflow if the branch is dirty?
To be able to get that behaviour, they recommend using prettier. I can get that hooked up here and in the API. |
I do think having a minimal set of shared formatting rules enforced in CI is a good idea. I don't really care what the formatting is, I'd just like for it to be minimally opinionated and automatically enforced. mainly just want PRs to be only related to the core logic that is changing and to not have to include formatting changes, which having some CI automation should enforce. |
I totally agree. I'm personally a fan of prettier, and it integrates smoothly with vscode. |
@EvanBoyle what do you think of that? |
@@ -0,0 +1,3 @@ | |||
{ | |||
"recommendations": ["esbenp.prettier-vscode"] |
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 will prompt devs to install the plugin.
🚢 |
https://github.com/cortexclick/cortex/pull/186