Open spinus opened 10 years ago
Well, currently I rely on various config parsers and their filter and pretty-print options. So my code does not understand a word of the config itself.
I'll totally take patches for new features as you describe, but cfgdiff has enough features for my personal usecase, so I probably won't invest much of my time for that.
My idea for that is, if you have code which understand config structure and can "sort" or whatever you can make another sub-tool for writing configs after "styling"/sorting. It could help not only to diff in nice way but also to keep the same "style" in different config files for the same application.
Sub-idea could be to make this package as "cfgtools" and inside could be tools like cfgdiff, cfgstyle, cfglint (maybe in the future). What do you think?