Closed bradhanks closed 8 months ago
Yeah, this is intentional.
We historically don't fix all the Credo issues in Credo's code and this is one of those cases where the warning does not bother me, but it "shows the check is working".
Another thing is that there are fixtures in test/
that will always yield issues and then we would different Credo configs inside Credo's codebase next to Credo's default config (which would then ironically not run on Credo).
Sounds great. Thanks for the context!
Credo has a warning there but it looks like it is intentional. Just wanted to check.
Warnings - please take a look
┃ ┃ [W] ↗ There should be no calls to IO.inspect/1. ┃ test/add_credo_plugin_to_project.exs:121:6 #()