I went through every ESLint code rule, and wrote down how the issue the rule tries to solve for #JavaScript applies to Elm. Result: almost none of them do. elmcraft.org/compare/javasc…

Solving annoyances in elm-review jfmengels.net/solving-annoya…

I'll be speaking on why you don't trust your linter at GOTO Copenhagen • IDLE ACCOUNT 😊 gotocph.com/2022/sessions/…

I just released a large release for elm-review. I decided to split the announcement into 2 parts. This first part focuses on the large performance improvements done to elm-review's automatic fix feature. I hope you'll enjoy the changes as much as I will! jfmengels.net/much-faster-fi…

I'm trying to learn from and help static analysis tool authors. If you're interested in making those tools better in any way — be it nice features, better performance, better user experience, etc — then please join me on the Static Analysis Tool Discord! discord.gg/sZ8jhAZMQ6

You might think: Elm is already so good, do I need elm-review? Here are some things that I've seen it being worth it:

Gaining insight into your Elm codebase with elm-review jfmengels.net/elm-review-ins…

Wrote an elm-review rule at work today for checking the naming of our Msg constructors. Spent 40 min discussing the naming convention rules and 5 min writing the actual code. That's how easy it is to create your own elm-review rule!

🚀 Preparing a new very nice release for elm-review 🚀

I wrote about how I view my work on elm-review and what keeps me motivated to work on it🎈 jfmengels.net/a-nice-round-b…

If you want to report a problem and really want to help, regardless of your domain, you need to explain 3 things: - What is the problem? - Why is it a problem? - How to solve the problem? And that's going to be hard if you try to be too succinct in your communication.

Devs often ignore the errors reported by the linter – even though the goal is the same:to ensure code works well Hear Jeroen Engels' talk about how language features impact the lint report, when should you ignore the linter and how to reduce false positives youtu.be/XjwJeHRa53A?li…

If you're someone who makes linters or works with them a lot, then you are exactly who this talk is meant for. I want linters to be awesome tools, and this talk "why you don't trust your linter" contains what I think are ways to make them much better than what they are today.

🌳#253: Ft. BramvdnHeuvel, Arthur Teisseire, miniBill (Leonardo), and Jeroen Engels. elmweekly.nl/p/elm-weekly-i… #elmlang

Because I think it will be be useful to linter authors like me, I wrote about implementing multi-file analysis in elm-review, which is one of the core features that make it so powerful and reliable. jfmengels.net/multi-file-ana…

A wild talk of mine appeared! Watch me talk about *why* we write linter rules (and why *you* should custom rules), as well as how and when. youtube.com/watch?v=zY1xDj…

elm-review as you know it (v2) turns 3 years old today! Time flied since this announcement: jfmengels.net/elm-review-v2/

How many linter rules are in your linter to do this mind-boggling number of code simplifications? In elm-review the answer is one. package.elm-lang.org/packages/jfmen…

🌳#262: Ft. Jeroen Engels, @[email protected], Dzuk, Elm Town & Jared M. Smith & Kevin Yank, Elm Online Meetup, Software Unscripted & @rhg_dev. elmweekly.nl/p/elm-weekly-i… #elmlang

In case you missed it, here is our discussion about Linter Configuration & Best Practices with guest speaker Jeroen Engels: blog.codacy.com/linter-configu… Check out the highlights, recording, Q&A & more. #linters #programming #coding #softwaredevelopment #codequality #opensource