Configuration handling

[qrrcnaxne]

I have a simple question about one of the code decisions in this project. I see you've chosen to not use the golang viper library for handling configuration and have a custom implementation with yaml library. I was wondering if there was a specific reason for this decision? Viper is compatible with cobra, written by the same author, so it would've been a good option?

[alajmo]

I think I looked at it at the beginning (actually for mani) but opted for my own since sake has more complex logic than a simple key-value config (supports nested config files, references to other objects, conditional specifications, etc.). So all of the features viper offers, it's easier for me to implement on my own, rather than find a way to use some of Viper's features.
With that said, I might in the future take another look at Viper for sake, and it seems like a good compliment to Cobra for certain projects.

[qrrcnaxne]

Hey yepp. Thanks a lot for answering. I really like the project. I've dabbled a little in something very similar but now I switched to using this sake. Great project!