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 rowanseymour on Thursday June 18, 2020 @12:57PM (#23565059)
It's been go-fmt that's converted me to this way of thinking. It's such a waste of time having a linter tell me after I've checked in code that I'm missing a space on line 123... please just add the space. Please let me and my colleagues never have to argue again about what is the right way to format something.
[ Parent | on HN ]
Re:GitHub Super Linter: one linter to rule them all by unfunco on Thursday June 18, 2020 @01:40PM (#23565515)
I feel the same, fmt is a productivity boon for me too.

There was a good quote from Rob Pike in his Go proverbs talk: "Gofmt's style is nobody's favourite, but gofmt is everybody's favourite."

[ Parent | on HN ]
Re:GitHub Super Linter: one linter to rule them all by FredrikMeyer on Thursday June 18, 2020 @01:31PM (#23565424)
Many linters have built-in auto-fix features like what you describe. (eslint, for example)
[ Parent | on HN ]
Re:GitHub Super Linter: one linter to rule them all by celticninja on Thursday June 18, 2020 @01:50PM (#23565644) 

    rubocop -a
For the win.
[ Parent | on HN ]
Re:GitHub Super Linter: one linter to rule them all by reledi on Thursday June 18, 2020 @06:31PM (#23568865)
Not the same experience as some of the best formatters out there. RoboCop is too configurable and too slow.
[ Parent | on HN ]
Re:GitHub Super Linter: one linter to rule them all by halostatue on Thursday June 18, 2020 @11:36PM (#23570693)
It would be nice if Rubocop didn’t need as much customization as it does, because it promotes styles that violate everything I have done in my 18 years of writing Ruby.

Some of its defaults? Fine, whatever. Others? They’re just _wrong_.

[ Parent | on HN ]