Credo.Check.Warning.Dbg: doesn't warn when using `&dbg/1` - Githubissues

rrrene / credo

A static code analysis tool for the Elixir language with a focus on code consistency and teaching.

http://credo-ci.org/

MIT License

4.91k stars 414 forks source link

Credo.Check.Warning.Dbg: doesn't warn when using `&dbg/1` #1138

Open mhanberg opened 2 months ago

mhanberg commented 2 months ago

Precheck

Proposals for new features should be submitted via: https://github.com/rrrene/credo-proposals
For bugs, please do a quick search and make sure the bug has not yet been reported here

Environment

Credo version (mix credo -v): 1.7.5
Erlang/Elixir version (elixir -v): Erlang/OTP 26 Elixir 1.16.3
Operating system: macOS 14.5

What were you trying to do?

I noticed that calls like |> tap(&dbg/1) are not triggering the warning

Expected outcome

capturing dbg/1 should emit the warning

Actual outcome

capturing dbg/1 should emits no warning