Suggestion : Better way of handling config errors?Suggestion

Dude. This is the umpteenth time this plugin has wiped a very customised config because of a misplaced comma. Is there maybe a way of handling a error that doesn't totally rest the data file. The Error echoes where in the config file the mistake is, just so I can see where I messed up but it doesn't leave the file for me to fix? : 

ServerInfo v0.5.8: Failed to load config file (is the config file corrupt?) (After parsing a value an unexpected character was encountered: ". Path 'settings.Tabs[0].Pages[3].TextLines[1]', line 74, position 5.)

I will look into it.