vrod
I have put some module attributes in my tests for easier reference, like this
@example Application.fetch_env!(:my_app, :thing)
but I notice I get errors when I run mix credo --strict:
Module attribute @example makes use of unsafe Application configuration call Application.fetch_env!/2
I am not understanding why this is unsafe?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Nicd
The value of the
@exampleattribute will be set at compile time and cannot be changed later. This is “unsafe” because it is easy to mistakenly think that it will follow the value configured at runtime, for example inconfig/runtime.exs, leading to hard to track errors.If you intend to set such a value at compile time, use Application.compile_env/3 available since Elixir 1.10.
vrod
Thank you for the explanation. I am still not sure why confusing == unsafe? This would means that many languages are “unsafe” haha. My understanding is that anything outside of a
do…endblock is evaluated at compile-time. But maybe this is my bad understanding – maybeApplication.compile_env/3does not works this way?Is possible to use ENV variable to inject code that gets compiled into the module in this way? For example
and then read that into a module or something like this?
Nicd
It’s possible but you would have to go out of your way to make it possible.
The meaning of “unsafe” here is different. The reason is that code like that can be confusing to a developer. They may expect that after they have built the application into a Mix release and transferred that to the server, that they can still change the value of the module attribute by changing the config, for example in
config/runtime.exs. But because module attributes are handled at compile time, this is not possible. So they may waste a lot of time not knowing why the config is not being read, or even not notice the problem at all until it causes a bug later.What
compile_envdoes is store the value at compile time, but also check at startup if there is another value configured (like inconfig/runtime.exs). If so, it will raise an error, thus alerting the developers that they have misunderstood how the config works and that they need to correct the issue.You can find more here: Elixir v1.10 released - The Elixir programming language