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

dbg uses in heex templates are not reported #97

Open
Munksgaard opened this issue Jan 19, 2024 · 1 comment
Open

dbg uses in heex templates are not reported #97

Munksgaard opened this issue Jan 19, 2024 · 1 comment

Comments

@Munksgaard
Copy link

I realize this may be impossible or outside the scope of what credo can do, but I thought it would be nice to have this (lack of) behavior recorded somewhere. Feel free to close the issue if you don't feel like it applies.

Environment

  • Credo version (mix credo -v): 1.7.3-ref.docusign-flow.9f6af01+uncommittedchanges
  • Erlang/Elixir version (elixir -v):

Erlang/OTP 25 [erts-13.2.2.5] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit:ns]

Elixir 1.16.0 (compiled with Erlang/OTP 25)

  • Operating system: NixOS unstable

What were you trying to do?

When using Phoenix, it is common to put heex templates in dedicated files, such as index.html.heex. It is possible to use dbg and other elixir functionality inside. Here's an example of the contents of a heex file:

<.link navigate={dbg("/")}>
      <.button>Go home!</.button>
</.link>

Expected outcome

Any uses of dbg are reported when running credo.

Actual outcome

Uses of dbg are not reported.

@rrrene rrrene transferred this issue from rrrene/credo Jan 30, 2024
@rrrene
Copy link
Owner

rrrene commented Jan 30, 2024

Hi, I am moving this issue here because in the issue template section you deleted, it says that "Proposals for new features should be submitted via: https://github.com/rrrene/credo-proposals".

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

No branches or pull requests

2 participants