Re:After 3 Months of JavaScript Linting, It's Pretty Much Al...
by slacka on Thursday August 03, 2017 @12:28PM
(#14921013)
Yes, just a kid crying about having to follow style guidelines. If manually running his team's tool is really wasting as much time as he claims, they should switch to a tooling that automatically corrects style. I use tabs, but the policy is spaces. When I commit a change, my my tabs are automatically controverted to spaces. Zero time lost and no one fights about tabs vs spaces.
[ Parent
| on HN ]
Re:After 3 Months of JavaScript Linting, It's Pretty Much Al...
by dang on Thursday August 03, 2017 @02:39PM
(#14922427)
> Yes, just a kid crying about
This breaks the HN guidelines against calling names in arguments, so please don't do that. Your comment would be just fine without the first sentence.
Re:After 3 Months of JavaScript Linting, It's Pretty Much Al...
by nulagrithom on Thursday August 03, 2017 @02:16PM
(#14922181)
Just a thought -- it would be neat to see a project that would allow you to check the code out again with your tabs instead of the committed spaces. More of a style translator than an enforcer.
Re:After 3 Months of JavaScript Linting, It's Pretty Much Al...
by xaedes on Friday August 04, 2017 @02:47AM
(#14926826)
It should be relatively easy to set up with git hooks:
Take one of the many Git Hooked Autoformaters: For example: https://github.com/michalrus/git-hooks-code-autoformat
Then add similar hooks for pulling on "post-merge" and "post-rewrite". There is no hook for "pull" per se, but either a merge or commit rewrite (rebase) happens after pull that changes code. So you should be good with those both hooks