Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
mhanberg opened this issue Jun 10, 2024 · 0 comments · May be fixed by #1158
Open

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

mhanberg opened this issue Jun 10, 2024 · 0 comments · May be fixed by #1158

Comments

@mhanberg
Copy link
Contributor

Precheck

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

@Nezteb Nezteb linked a pull request Nov 3, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant