I have a conceptual question about settings and would like to ask you to clarify some points, if you don't mind.
When we are editing local settings (that merge/override the root ones), we have the following behaviour:
- Changed (at this level) settings are displayed as bold
- Changed (at this level) settings are saved in current-level config
But when we are editing root settings we have the different behaviour:
- When change settings, they began being displayed as bold
- When we save them, they are being written into root-level config
- When we open them for the second time - they aren't displayed as bold any more
(In fact, there are some bugs in editing root settings, but let's not to pay attention to them right now. I'm trying to understand the whole idea)
As I understand StyleCop's settings architecture, we can distinguish the following levels:
- default values (defined in analyzer assembly)
- root config
- local config 1
- local config 2
When we open the epmty root config file - we see default settings (actually taken out from assembly).
So don't you think that it would be nice to always show settings as bold if they defined in current-level config (even it is a root config)?
In other words, to display all non-default settings as bold when editing root config (in fact, it already works in this way for local configs, but not for the root one).
Thanks in advance!
P.S. Just let me know if I failed to express my idea in a understandable way.