Using Credo to improve your Elixir code | What did I learn
At the beginning of my Ruby on Rails career, I was using the “Rails Best Practices” code metric tool. The intent of the tool is pretty simple. It provides you suggestions how to improve your code. The best part of it, that on the https://rails-bestpractices.com website I was able to find detailed instructions why and how to fix those issues. I love that tool. I was using it every day to check my c
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
https://github.com/rrrene/credo/blob/b61364c462c1f2113d20416a442c74945b2a8de4/CHANGELOG.md
mixでプロジェクトを作ったときに最初にやること
Credo: Looking at 1.0 and beyond · rrrene
Elixir Code Quality Tools · Matt Gauger
https://github.com/rrrene/credo/blob/master/CHANGELOG.md
Credo v0.7.4 released
Use `credo` Linter in Git `pre-commit` Hook
Credo v0.7.1 released
Credo v0.6.0 released
Does your company use Credo? · rrrene
Credo v0.4.13 released - Elixir Code Analysis
GitHub - rrrene/credo: A static code analysis tool for the Elixir language with a focus on code consistency and teaching.
