(But we have no support for the actual config file...
# tornadofx
e
(But we have no support for the actual config file being in json format - yet)
n
So should I try to rework the PR to get rid of the
Context
an add a way to access the configs easily or do you want to try out stuff first? And should I change the config object so that we can plug in different back ends like json or properties.
e
Yeah, I think we absolutely could change out the underlying Properties object with a Config object which has a similar API. Then we can simply add a format enum which can be configured on the Config object to determine if we should save as Properties or JSON. What do you mean by a way to access the configs easily? I think we have that already. For example, accessing the global config is now just
app.config
and to access any other class's config object you'd do the same, or
find<OtherComponent>().config
.