You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2018. It is now read-only.
Using this framework it is possible to load an entire config file into a object. However, it appears to be all or nothing. I can't, for example, load parts of the configuration into separate objects. For example:
{"logging" : {/*options for logging here*/}"printing" : {/*options for printing here*/}"otherStuff" : {/*options for xxx here*/}"moreStuff" : {/*options for yyy here*/}}
I suppose I could just create one container object that has these other objects within it, but might be nice to support loading these partial object directly so the DI's are all separated. Or, I guess I could create multiple log files, but that seems messy as well.
Rationale: I like each framework to be completely independent of the other frameworks (like logging). So, the log framework would get it's log settings independent of the others.
The text was updated successfully, but these errors were encountered:
Using this framework it is possible to load an entire config file into a object. However, it appears to be all or nothing. I can't, for example, load parts of the configuration into separate objects. For example:
I suppose I could just create one container object that has these other objects within it, but might be nice to support loading these partial object directly so the DI's are all separated. Or, I guess I could create multiple log files, but that seems messy as well.
Rationale: I like each framework to be completely independent of the other frameworks (like logging). So, the log framework would get it's log settings independent of the others.
The text was updated successfully, but these errors were encountered: