akutz / gofig

75%

master: 75%

LAST BUILD ON BRANCH feature/viper-nofork-yaml

branch: feature/viper-nofork-yaml

CHANGE BRANCH

x

Reset

• feature/viper-nofork-yaml
• bugfix/copy-scope
• bugfix/explicit-names
• bugfix/pflag-compile
• bugfix/scope-parent
• bugfix/test-pflag-builds
• feature/gotil
• feature/interfaces-opt-pflag
• feature/multi-regs
• feature/override-registrations
• feature/rm-pflag-tag
• feature/scope
• feature/scope-with-prefix
• feature/scoped-prefixes
• feature/secure-json
• feature/yaml-validation
• master
• v0.1.0
• v0.1.1
• v0.1.2
• v0.1.3
• v0.1.4
• v0.1.5
• v0.1.6
• v0.1.7
• v0.1.8
• v0.1.9

Use Primary Viper Repo, New YAML Fork/Branch

This patch updates GoFig to use the primary Viper repository, no longer
depending upon the akutz fork for specific support. However, this patch
also updates the YAML dependency from one forked branch to another. This
new branch is linked to a PR, https://github.com/go-yaml/yaml/pull/185,
which enables the Go-YAML library to preserve JSON codec compatibility
when unmarshaling data from YAML configuration files. Without this
dependency, data unmarshaled with Go-YAML into Viper cannot then be
marshaled to JSON and back again since by default Go-YAML uses
map[interface{}]interface{} as its internal map type. Since the JSON
codec does not support the interface{} type as a key, attempts to
marshal data to JSON that was unmarshaled from YAML using the Go-YAML
library fails.