It has been a while since I religiously used Credo but I have to say that if I understand that rule correctly then I disagree with it. If for no other reason than this thread exactly: it’s completely valid to start a pipe with a value that’s generated by a function i.e. Ecto.Multi.new().
dimitarvp
0
andyleclair
We don’t use that rule at work (we cp from project to project maintain a custom set of credo rules), it’s one of the most annoying rules. For my personal projects, I don’t use Credo at all!
0
dimitarvp
Yeah same, I use Credo as an advisor a few times and then just drop it. It’s been helpful but not by a lot.
0
sodapopcan
I like the suggestions for when I accidentally do stuff like:
|> Enum.flatten()
|> Enum.map(& &1.foo)
And credo is like, “You dummy, just use flat_map!” It’s especially nice when you upgrade Elixir and it shows you all the places you can improve with stuff in the new version.
…though I suppose this “artificial intelligence” everyone keeps talking about can also do that.
I do like the linting a lot, I just disable a bunch of checks.
1
dimitarvp
I should have probably said this because this is what I ended up doing in my last 3 projects.
0
