Contemplating removing all but YAML configuration files ... input wanted

[jeffaco]

Since I have no real way to reach my user base, I thought I'd open an issue here.

Currently, duplicacy-util supports reading configuration files in a large variety of formats due to use of Viper. Viper allows configuration files to be in JSON, TOML, YAML, HCL, or Java properties config files. I've always used YAML, and to be best of my knowledge, I never came across anyone that used something else.

I'm contemplating dumping Viper and just sticking to YAML. The problem is that Viper pulls in the kitchen sink (there's a huge number of dependencies). I think fewer dependencies means fewer code paths, which means smaller images and greater reliability.

But I can only do that if folks are only using YAML configuration files.

Do you use something other than YAML for duplicacy-util configuration files? If so, reply here!

[dengelsma]

I only use YAML. Getting rid of viper would not affect me.

[wdckwrth]

Newish duplicacy-util user here. Thought you might like more than a sample of 1.

I only use YAML.

[mightymightys]

The adavantes of dumping viper far outweigh the disavantage of being "obliged" to use the YAML format. For the small amount of configuration that's necessary here, that's a trivial adaptation even if one is used to anothter format. So go for it!

[mayerwin]

Yes please do.

[Sxderp]

YAML or JSON. Since YAML is supposed to be a superset of JSON any decent YAML parser should handle it.