deferred_config icon indicating copy to clipboard operation
deferred_config copied to clipboard

(older project) support '{:system...}' and ':apply {m,f,a}' patterns in OTP apps

Results 5 deferred_config issues
Sort by recently updated
recently updated
newest added

The bugs occur when you want to use an environment variable for boolean config and the default is `true`. For example: ``` bool_conf: {:system, "BOOLEAN", true, {String, :to_atom}} ``` The...

Fixes compiler warnings for unused variables in the `walk` function clause

- [x] Update all packages. - [x] Add code formatter. - [x] Fix all warnings.

I was looking for some guidance on how to properly use deferred_config when running mix tasks. In particular this is for running ecto tasks. First, here is my test config....

Pass `persistent: true` to `Application.put_env/4`, so that the new config values will survive the application load and reload events. Documented [here](https://hexdocs.pm/elixir/Application.html#put_env/4). As example, it's used by [`Mix.Config.persist/1`](https://github.com/elixir-lang/elixir/blob/v1.4.5/lib/mix/lib/mix/config.ex#L237-L244).