We're working on a multi-tenant app and would like more fine-grained control over how config is stored. Since LocalSettingsRepository is final, we're not able to extend it to modify (see #222 for a previous attempt to make it extendable).
I respect the decision to keep everything final, so instead I propose creating a contract for the LocalSettingsRepository, so package users may bind their own implementation to the IoC.
What problem is this fixing?
Provides more control over local configuration storage, useful when dealing with multiple environments (see #123) or multi-tenant applications.
Describe your change
We're working on a multi-tenant app and would like more fine-grained control over how config is stored. Since
LocalSettingsRepository
isfinal
, we're not able to extend it to modify (see #222 for a previous attempt to make it extendable).I respect the decision to keep everything
final
, so instead I propose creating a contract for theLocalSettingsRepository
, so package users may bind their own implementation to the IoC.What problem is this fixing?
Provides more control over local configuration storage, useful when dealing with multiple environments (see #123) or multi-tenant applications.