News for hackers. Stuff that matters.

A comment on GitHub Super Linter: one linter to rule them all. Parent comment

Re:GitHub Super Linter: one linter to rule them all by est31 on Thursday June 18, 2020 @09:28PM (#23570105)
Most autoformatters are under active development, and updates to them often causes changes in their behaviour. So you have to have all devs agree on the precise version of the formatter used, and even then you still need to do regular commits that contain nothing but a run of the newest version of the formatter on the codebase, which sadly destroys long term git blame.
[ Parent | on HN ]
Re:GitHub Super Linter: one linter to rule them all by zetafunction on Thursday June 18, 2020 @11:42PM (#23570727)
Chromium has a presubmit that enforces that code is autoformatted. However, it only enforces this for changed lines, and in practice, it works pretty well.
[ Parent | on HN ]
Re:GitHub Super Linter: one linter to rule them all by cheez on Thursday June 18, 2020 @09:52PM (#23570216)
this is a solved problem, pin your packages.
[ Parent | on HN ]
Re:GitHub Super Linter: one linter to rule them all by est31 on Thursday June 18, 2020 @10:23PM (#23570391)
But you still have to update them every now and then otherwise you can't use new features of your language. Which gives you the issue of breakages again.
[ Parent | on HN ]
Re:GitHub Super Linter: one linter to rule them all by waheoo on Thursday June 18, 2020 @10:52PM (#23570506)
I dont think people want to hear that there are still problems with autoformatting text.

Anyway, my point still stands, drop rules about line length and rules that care about inter line break positions and most of these problems go away.

[ Parent | on HN ]
Re:GitHub Super Linter: one linter to rule them all by cheez on Thursday June 18, 2020 @11:00PM (#23570535)
Sure. Most large teams do this on a 6 month basis or when it is needed to implement something. Again, a solved problem.
[ Parent | on HN ]