-
-
Notifications
You must be signed in to change notification settings - Fork 354
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
Prettier cmd #481
Prettier cmd #481
Conversation
So seems to work properly. Also regarding the ci: This triggers me, because it throws errors but the CI is not blocked. Which is wrong no? Or maybe we could just disable those rules. |
Hmm, yeah it's always done that though. I don't know if I consider console, real errors. We can just disable the eslint rule. |
The console log rule can be deleted IMO |
I think it's just a matter of setting it off. Right now it's using development/production to decide the rule. If you delete it, it defaults to on |
was meaning setting it to:
|
yeah, do it. |
Done |
@zekth can you rebase this one and let's try and get it merged. |
@yanfali done |
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.
lgtm
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.
lgtm
Following: #480
Here is the addition of raw prettier commands because we are experiencing different behaviours using the vue-cli commands.
Here 2 commits, one pushing the commands, another pushing the modifications using the
prettier --write
.Want to run it througth travis to see its behaviour