You should not use SetConfigFile. Its documentation says:
> SetConfigFile explicitly defines the path, name and extension of the
> config file.
> Viper will use this and not check any of the config paths.
You should use SetConfigName instead and pass it "settings", without
extension. Its docume
You can try using https://github.com/kisielk/godepgraph. Its a great tool.
In combination with GraphViz it can produce dependency graphs in various
formats.
Of course, you can always do something among the lines of go list -f
'{{.Deps}}', but I do not believe it will give you graph, only list o
Hi everybody.
I would like to get some feedback on set of libraries that I wrote.
Together they are pluggable, middleware-based HTTP client.
Main idea is to replicate pattern from widely used for server
implementation. We all know (and love) http.Handlerinterface, which is a
base for bunch
