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

Elixir 1.17 compiler warning: Req is not defined #1102

Open
jaimeiniesta opened this issue Nov 26, 2024 · 0 comments
Open

Elixir 1.17 compiler warning: Req is not defined #1102

jaimeiniesta opened this issue Nov 26, 2024 · 0 comments

Comments

@jaimeiniesta
Copy link

Elixir 1.17 raises a compiler warning that Req is not defined. We don't use Req in our project, and it's an optional dependency, so it should be silenced in this case.

Environment

  • Elixir & Erlang versions (elixir --version):

Erlang/OTP 27 [erts-15.1.2] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit]

Elixir 1.17.3 (compiled with Erlang/OTP 27)

  • ExAws version mix deps |grep ex_aws
* ex_aws (Hex package) (mix)
  locked at 2.5.7 (ex_aws) 2c3c5775

* ex_aws_s3 (Hex package) (mix)
  locked at 2.5.5 (ex_aws_s3) ac34af1e
  • HTTP client version. IE for hackney do mix deps | grep hackney
* httpoison (Hex package) (mix)
  locked at 2.2.1 (httpoison) 51364e6d

* hackney (Hex package) (rebar3)
  locked at 1.20.1 (hackney) fe9094e5

Current behavior

We get this compiler warning:

==> ex_aws
Compiling 28 files (.ex)
    warning: Req.request/1 is undefined (module Req is not available or is yet to be defined)
    │
 24 │     |> Req.request()
    │            ~
    │
    └─ lib/ex_aws/request/req.ex:24:12: ExAws.Request.Req.request/5

Expected behavior

Not to get this compiler warning when we're not using Req, as it's an optional dependency.

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

1 participant