Closed Licenser closed 10 years ago
After reading the source I see that some of this is already provided by the way one can check for multiple schemas. This only leaves open the question what would be the best practice on handing this with different application veriosions and releases.
It would be sweet if it were possilbe to have something like an {include, module} (and/or {include, "top.namespace", module} ) statement that then would pull config definition out of a predefined function (much like the behaviour_info works)
That way libraries could include their config parameters and the autor of a application using (i.e. bitcask, elveldb, lager) would not have to reinvent the wheel (or copy and paste form another app) but could just say {include, lager}
and the lager.erl would export cuttlefish_info(mappings) -> {...} and cuttlefish_info(translations) -> {...}