The latter.
I want to have a certain, “static” set of configs later on.
That set is just so big and full of dependencies that I want to have a clean architecture that lets me rather easily and in a readable format add new configs, which should then be easily managed (as in, reset to a certain value under certain conditions etc.)
So if I have 10 configs, later decide to add a new config because of a new feature, I do not want to “hardcode” how the new config behaves together with all the other configs, as that severely bloats the code.
I want to do something like creating a new object (the config), then overwrite a reset function where I hardcode the reset value, and then have a few other attributes that determine when this value will get uneditable and/or reset etc.
If that is not possible, something else along those lines.