Skip to content

Resolve CLI elixirc warnings #10459

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

Merged
merged 2 commits into from
Feb 1, 2024
Merged

Resolve CLI elixirc warnings #10459

merged 2 commits into from
Feb 1, 2024

Conversation

the-mikedavis
Copy link
Collaborator

Most of the elixirc warnings in the CLI are benign. There are a few cases where I believe a variable was meant to be an atom instead though, which should change some error-handling behavior slightly.

I've also added a bazel test for running mix compile --warnings-as-errors so these can be caught by the CI in the future.

This test should fail when `mix compile --warnings-as-errors` gives
any warnings.
* Remove unused aliases/imports
* Remove or underscore unused bindings
* Fix variables that should be atoms (`unavailable` -> `:unavailable`)

Also, `Logger.warn/1` has been replaced by `Logger.warning/1`. It should
be safe to just replace the call with `Logger.warning/1` since it's
been in the standard library since Elixir 1.11.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants