What I'm missing is a really good linter and auto-formatter for PostgreSQL or just standard SQL. Haven't found something that seems well established and well made.
GitHub Super Linter: one linter to rule them all
81–90 of 360 posts
Re: GitHub Super Linter: one linter to rule them all
#82Earlier quoted context omitted.
I can wholeheartedly recommend Black for Python, gofmt for Go, and terraform fmt for Terraform. What are some other great formatters out there?
Another recommendation for Black. I use 'black -l 120' because the default PEP recommended 80 chars per line is too restrictive.
Black uses a 88 char per line limit. In the course of normal Python coding I rarely hit it.
For public code I do not recommend changing the defaults since it may make PRs a mess.
Re: GitHub Super Linter: one linter to rule them all
#83What's very interesting in the list here: https://github.com/github/super-linter/#supported-linters Java is the only major language without any sane default coding standard (no, google-java-format is google-specific, outdated, not up-to-date with recent versions and not maintained by community). It's a pity really.
Java is going downhill(as in not much new code is being written in it), so of the mainstream languages is going to get supported last if ever.
> Java is going downhill(as in not much new code is being written in it)
This is just completely false.
- https://madnight.github.io/githut/#/pull_requests/2020/1
- https://insights.stackoverflow.com/survey/2020#technology-pr...
I could link many other links showing Java as an extremely widespread language. There is just nothing comparable in the corporate world.
Re: GitHub Super Linter: one linter to rule them all
#84Earlier quoted context omitted.
It's kind of odd that GitHub is asking people to pull an image from a Docker account that most people won't recognize (admiralawkbar/super-linter), as opposed to an official GitHub one.
What was Admiral Ackbar's famous quote?
“ask yourself if that answer doesn't make you look just a bit like a dewback's cloaca”
Re: GitHub Super Linter: one linter to rule them all
#85Earlier quoted context omitted.
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.
Many linters have built-in auto-fix features like what you describe. (eslint, for example)
rubocop -a
Re: GitHub Super Linter: one linter to rule them all
#86Is anyone else uncomfortable with Github/MS owning more and more of your tool chain? Maybe my lock-in radar is faulty, but the more this happens, the more scared I get.
It’s MIT License. You’re free to fork.
Re: GitHub Super Linter: one linter to rule them all
#87Great! Now do it for code formatters! After using Prettier for a few years I'm firmly in the camp of mandatory/enforced code formatters. As long as it's a half decent formatter like Prettier I believe my personal opinions on the specific formatting choices are much less important than essentially never having to think about formatting again, in particular having to ask people to fix formatting in code reviews (or fix…
One of the hills I am willing to die on is auto-formatting. Code formatting is easily automated to an acceptable level, and people's personal preferences are subjective.
I like to solve interesting problems, and concentrate on crafting high quality software. Manual code formatting contributes to neither of these disciplines. Code formatting is BORING robot work, not human work. Total pointless drudgery. Toiling away because you like your bracket with a different spacing is IDIOTIC. Run the formatter and move on.
Re: GitHub Super Linter: one linter to rule them all
#88Is anyone else uncomfortable with Github/MS owning more and more of your tool chain? Maybe my lock-in radar is faulty, but the more this happens, the more scared I get.
I am starting to feel this way about just git.
Re: GitHub Super Linter: one linter to rule them all
#89What's very interesting in the list here: https://github.com/github/super-linter/#supported-linters Java is the only major language without any sane default coding standard (no, google-java-format is google-specific, outdated, not up-to-date with recent versions and not maintained by community). It's a pity really.
Java is going downhill(as in not much new code is being written in it), so of the mainstream languages is going to get supported last if ever.
This is an inane comment, there's TONS of new code being written in it, probably more than any other language. Outside the HN bubble of Rust/Draco/OCaml companies tend to stick with the Java/JS/Ruby/C# languages.