Not my call anyway, I just clean up here 
2 Likes
For the most part I would agree with you but I’ve had a lot of luck with automating unit and functional tests with huge amounts of time freed up and generally very precise indications of where the problems have come in.
FWIW, there are two issues complicating checking of config files:
- We use an external library for parsing the config file, and there isn’t much desire to reimplement that library for a few minor tweaks in behavior.
- I don’t know of any user that would intentionally override an option in a later config section. (This does cause confusion for users and this is not the first report I’ve seen of it.) However, there are many users that would like to be able to duplicate a config section multiple times and only set some options in each instance of that config section. The “ratrig configs” are an example of this. More recent versions of the python config parsing libraries do have the ability to prevent duplicate config sections, but don’t (to my knowledge) have the ability to flag just duplicate options in duplicate config sections.
Cheers,
-Kevin