GitHub Super Linter: one linter to rule them all

Re:GitHub Super Linter: one linter to rule them all by michaelmior on Thursday June 18, 2020 @12:52PM (#23564995)

I agree with sentiment but I don't think it's entirely true that it only affects reading code. When it comes to modifying existing code, I have to deal with whatever format the existing code was written in. For example, personally I hate working with code with tabs so I would find this frustrating. (As an aside, I'll admit this is really my problem and a rather silly one.) Of course one solution is to transform code on read to the current user's preferred format and then back to the canonical format on commit. Although this seems potentially error prone.

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by ambicapter on Thursday June 18, 2020 @01:19PM (#23565286)

> When it comes to modifying existing code

You don't have to deal with anything as long as you're using the same formatter everyone else is using.

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by michaelmior on Thursday June 18, 2020 @01:24PM (#23565347)

My point was that when writing new code, I can write it in whatever format I want knowing that it's going to be formatted the canonical way. But when modifying code, I have to work with code in one specific format that may not be my preferred format.

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by asutekku on Thursday June 18, 2020 @01:29PM (#23565406)

Can’t you just set up a linter/formatter to your style, apply it to your style when editing and on save set it to the project style?

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by kevin_thibedeau on Thursday June 18, 2020 @01:40PM (#23565516)

It fucks up the diffs in the codebase.

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by michaelmior on Thursday June 18, 2020 @01:55PM (#23565698)

How so? If the canonical format is applied every time you save, you'll always be doing a diff with files using the same format. Of course, it does mean the code in the diffs may not be in your preferred format.

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by kevin_thibedeau on Thursday June 18, 2020 @01:57PM (#23565714)

If you want to diff against anything in the past you get a bunch of formatting noise that occludes real changes.

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by dtech on Thursday June 18, 2020 @03:47PM (#23567070)

Usually when introducing such a tool you do 1 commit that reformat the whole codebase to the new style and then automatically enforce it.

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by erichurkman on Thursday June 18, 2020 @06:33PM (#23568891)

And in those large reformat commits, add a file like `.git-ignore-revs-file` that is checked in, so you can configure git to ignore that revision and pretend it never existed:

    [blame]
      ignoreRevsFile = ".git-ignore-revs-file"
      markIgnoredLines
      markUnblamableLines

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by dtech on Friday June 19, 2020 @05:02AM (#23572599)

That's an incredibly useful trick to know

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by mcgoo on Thursday June 18, 2020 @03:03PM (#23566468)

This is something that keeps coming back to me either as a feature or as a product of some kind - a tool that can stop this from getting in our way.

The simplest and safest would be to apply the formatter to both the old and the new copy before diffing it. It ceases to be the actual difference at that point, but there are definitely two distinct use cases for diffs - one for humans to read and one for the machine to apply.

The other case that would be amazing but even more of a stretch would be to rewrite the entire history. It seems like there is a spot for "different views of history" and you could do a no-difference merge to join the to histories as of now so that the actual history did not get lost. As I write this, it starts to sound like just a caching system for the idea above.

This needs a highly reliable formatter of course... I have on occasion had code broken when formatting.

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by michaelmior on Thursday June 18, 2020 @02:26PM (#23566043)

If you're talking about moving from a codebase that did not use a consistent formatting style or a style that did not match the auto formatter configuration, sure. I was assuming a case where automatic formatting was done from the start.

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by peterstensmyr on Thursday June 18, 2020 @07:17PM (#23569220)

Git has an option to ignore certain commits when doing a git blame, —ignore-revs. You can also point it to a file with —ignore-revs-file <file>. You can configure this per project with git config ignoreRevsFile .git-blame-ignore-revs. After doing this, you get nice diffs AND nice looking code. The price to pay is that every developer has to run one git command locally.

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by libria on Thursday June 18, 2020 @02:22PM (#23565990)

I feel like this is a team preference problem and not a formatter problem. The formatter will only do what you tell it, spaces or tabs.

Looking at this another way, formatters are designed to "frustrate" devs into working only 1 way. If you think it's more helpful to have a codebase with mixed spaces/tabs with commits that express each developer's unique flair, then a formatter is not for your team.

[ Parent | on HN ]

Re:GitHub Super Linter: one linter to rule them all by VectorLock on Thursday June 18, 2020 @05:28PM (#23568231)

Formatters are a way for one person who likes the formatters output to enforce their will on other who might not necessarily like that.

[ Parent | on HN ]