v0.0.144

fix(tracing): ignore health endpoints (#189)

v0.0.143

refactor: improve decoderx wording for parse errors (#187)

v0.0.142

feat: add x-total-count to pagination headers (#186)

See https://github.com/ory/hydra/issues/1666

v0.0.141

fix(clidoc): improve link generator (#184)

v0.0.140

feat: add clidoc helpers (#183)

v0.0.139

fix(logrusx): prettify on json_pretty only (#182)

v0.0.138

feat: add debug config dumping to viperx (#175)

v0.0.137

fix: removing whitespaces in config file path (#173)

This fixes simply trims whitespaces from the configuration file path if one has been specified -c // --config flag. 
This fixes a problem if you try to run e.g. Kratos and specify a custom configuration will with -c // --config flag without specifying each part of the commandline call as a seperate string literal: 

`kratos serve "-c ./myconfig.yml"`

fails with the following error message, although the file exists and the process has sufficient permissions to read the file:

`Unable to open config file. Make sure it exists and the process has sufficient permissions to read it  audience=application error=map[message:open  ./myconfig.yml: no such file or directory] path= ./contrib/quickstart/kratos/email-password/.kratos.yml service_name=kratos service_version=`

This is caused by the handling of flags as defined by https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html, which results in a whitespace in the beginning of the config file path. 

As the error message is misleading and it is easy to overlook the whitespace in the error message, the fix simply removes whitespaces from the file path before it gets passed to viperx.

v0.0.136

fix(reqlog): resolve broken test

v0.0.135

feat: add helpers for viper unstructured config (#170)