Luca Salvarani

My problem is that the `new_config.toml` file is handled by the user which could lead to many "invisible" errors if they forgot to add `dynaconf_merge = true`. Any ideas? Otherwise...

> You can use `merge_enabled=True` on the dynaconf instance to force global merge, then dynaconf will consider `dynaconf_merge` on every loading data. > > https://www.dynaconf.com/configuration/?h=merge_enabled#merge_enabled Maybe I didn't get that...

> In your case, I think the best option for now until we have custom merging strategies is to define a custom loader, > disable the builtin toml loader, write...

Thanks @rochacbruno, I finally managed to make it work! 🎉 In the end I did it differently though, by **exporting** the current configuration as a dictionary and **merging** it to...

An even cleaner way to overcome the problem is to subclass the `Dynaconf` object and define a `reload_settings` method: ```python from dynaconf import Dynaconf as _Dynaconf, Validator class Dynaconf(_Dynaconf): def...

Thank you @pedro-psb! > In the meantime, I've found a small hack that can be used as a workaround as well. You can use when + cast to set a...

Sorry I'm a bit confused, shouldn't the actual solution to use the `apply_default_on_none` as told in the documentation? If so, this is a bug right?

> Also, one possible way to improve user experience in this use case is to add an "interpret-empty-str-as-none" option. I personally don't like it, as we already have the `@empty`...

> The `Nested` field only uses the value of the attribute and not the whole object when marshalling with the nested model. > > Probably the easiest solution is to...

Stesso problema di #49