If my understanding is correct settings are only persisted should they differ from default values declared in your settings provider. I really don't think this is good practise, it may be necessary to read the database for analytics and debugging purposes. The system has to read the database to see if it holds the default value, why then delete it?
Surely settings should be persisted at all times?
3 Answer(s)
-
0
@BobIngham this is a design choice actually. This is done for performance issues I guess. You are right about debugging purposes it would be nice to see the values on the database but making such a change would be a breaking change.
-
0
@ismcagdas, thanks for getting back. One of the things I like about working with your solution is your diligent attention to all github and forum posts. I don't want to suggest a breaking change when you have other priorities. I can work without this feature but it took me a while to figure out what was happening. I use the settings feature a lot for tenant parameters and the absence of settings in the database just makes it a little bit difficult to work out what's going on when working with third party data providers. Thanks again, keep up the good work!
-
0
@BobIngham I also think this behavior is confusing sometimes. We will keep this in mind for the next releases.
