Yes, that code would go into the library and then you don’t HAVE to add config :test_lib, ... into your application config.
Does that answer your question?
wolf4earth
0
xgeek116
@wolf4earth , not really , I didn’t get the difference between :
@default [your: “default config”]
and
@default_config
Espacially the “your”
0
wolf4earth
This is just an example using a module attribute (used as constant - think of JavaScript’s const). There’s no special meaning behind it.
The important part is that you can use Application.get_env/3 to set defaults and don’t NEED to set the configuration values in config/ - assuming you can provide reasonable defaults.
0
xgeek116
Here :
Application.get_env(:test_lib, :dev, @default_config)
the Library will get the env variables from where exactly (:test_lib and :dev) ? How it will fetch it besides putting values in config/ ?
0
wolf4earth
I’d suggest to go through the official docs.
And here is the documentation for Application.get_env/3:
1
karlosmid
Had the same issue. In mix.exs deps part, we can change library default :prod value with :env parameter:
0