elm-review (@elmreview) profile picture

elm-review news and announcements. https://nitter.cf/t.co/cYkEmwVGBK Created & managed by @jfmengels

Joined July 2020
Photo by elm-review (@elmreview)Photo by elm-review (@elmreview)Photo by elm-review (@elmreview)Photo by elm-review (@elmreview)Photo by elm-review (@elmreview)Photo by elm-review (@elmreview)Photo by elm-review (@elmreview)Photo by elm-review (@elmreview)
elm-review retweeted
In case you missed it, here is our discussion about Linter Configuration & Best Practices with guest speaker @jfmengels: blog.codacy.com/linter-confi… Check out the highlights, recording, Q&A & more. #linters #programming #coding #softwaredevelopment #codequality #opensource
3
3
575
How many linter rules are in your linter to do this mind-boggling number of code simplifications? In @elmreview the answer is one. package.elm-lang.org/package…
1
6
413
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=zY1xDjGE…
2
1
8
511
Because I think it will be be useful to linter authors like me, I wrote about implementing multi-file analysis in @elmreview, which is one of the core features that make it so powerful and reliable. jfmengels.net/multi-file-ana…
3
5
11
1,551
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.
Devs often ignore the errors reported by the linter – even though the goal is the same:to ensure code works well Hear @jfmengels' talk about how language features impact the lint report, when should you ignore the linter and how to reduce false positives youtu.be/XjwJeHRa53A?list=PL…
2
8
1
24
4,798
elm-review retweeted
Devs often ignore the errors reported by the linter – even though the goal is the same:to ensure code works well Hear @jfmengels' talk about how language features impact the lint report, when should you ignore the linter and how to reduce false positives youtu.be/XjwJeHRa53A?list=PL…
5
2
23
6,672
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.
1
1
3
540
🚀 Preparing a new very nice release for @elmreview 🚀
2
1
20
973
Wrote an @elmreview 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!
1
4
23
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:
2
6
15
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
1
3
4
I just released a large release for @elmreview. I decided to split the announcement into 2 parts. This first part focuses on the large performance improvements done to @elmreview's automatic fix feature. I hope you'll enjoy the changes as much as I will! jfmengels.net/much-faster-fi…
1
10
1
25
I went through every @geteslint code rule, and wrote down how the issue the rule tries to solve for #JavaScript applies to @elmlang. Result: almost none of them do. elmcraft.org/compare/javascr…
2
14
1
41