Check running by default?
Environment
- Credo version (
mix credo -v): 1.7.0 - Erlang/Elixir version (
elixir -v): checked multiple versions - Operating system: MacOS
What were you trying to do?
I was trying to run all my checks, which do not include Credo.Check.Warning.MissedMetadataKeyInLoggerConfig at all, so this check shouldn't be giving me issues.
Expected outcome
No issues
Actual outcome
Logger.metadata will be ignored in production.
This seems like a 1.7.0 only issue, 1.6 versions didn't give me this problem.
Can you post the .credo.exs of the project you are having this issue in?
@gemantzu Checking in: Any news on this?
I was seeing this too, but I realized some checks now have a "this check is enabled by default" banner that I hadn't known to look for (as of credo 1.7.4). https://hexdocs.pm/credo/Credo.Check.Warning.MissedMetadataKeyInLoggerConfig.html
Just to be clear: There has been a set of default checks from the start and which checks are "on by default" has been evolving over the years.
An important feature, introduced in Credo 1.6, is the ability to explicitly enable only the checks you want.
Closing this as expected behaviour. Please re-open if you disagree! 👍