f3a05eb800
Some warnings about go1.16 compatibility, so including them here: + go mod tidy -modfile=vendor.mod github.com/docker/cli/cli/registry/client imports github.com/docker/distribution/registry/api/v2 imports github.com/gorilla/mux loaded from github.com/gorilla/mux@v1.7.0, but go 1.16 would select v1.8.0 github.com/docker/cli/cli/compose/loader imports gopkg.in/yaml.v2 tested by gopkg.in/yaml.v2.test imports gopkg.in/check.v1 loaded from gopkg.in/check.v1@v1.0.0-20200227125254-8fa46927fb4f, but go 1.16 would select v1.0.0-20201130134442-10cb98267c6c github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/Shopify/logrus-bugsnag loaded from github.com/Shopify/logrus-bugsnag@v0.0.0-20170309145241-6dbc35f2c30d, but go 1.16 would select v0.0.0-20171204204709-577dee27f20d github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server/storage imports gopkg.in/rethinkdb/rethinkdb-go.v6 imports github.com/opentracing/opentracing-go loaded from github.com/opentracing/opentracing-go@v1.1.0, but go 1.16 would select v1.2.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server/storage imports gopkg.in/rethinkdb/rethinkdb-go.v6 imports github.com/opentracing/opentracing-go/ext loaded from github.com/opentracing/opentracing-go@v1.1.0, but go 1.16 would select v1.2.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server/storage imports gopkg.in/rethinkdb/rethinkdb-go.v6 imports github.com/opentracing/opentracing-go/log loaded from github.com/opentracing/opentracing-go@v1.1.0, but go 1.16 would select v1.2.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports github.com/spf13/afero loaded from github.com/spf13/afero@v1.1.2, but go 1.16 would select v1.2.2 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports github.com/spf13/cast loaded from github.com/spf13/cast@v1.3.0, but go 1.16 would select v1.3.1 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports github.com/spf13/jwalterweatherman loaded from github.com/spf13/jwalterweatherman@v1.0.0, but go 1.16 would select v1.1.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports gopkg.in/ini.v1 loaded from gopkg.in/ini.v1@v1.51.0, but go 1.16 would select v1.56.0 github.com/docker/cli/cli/command imports github.com/theupdateframework/notary/client tested by github.com/theupdateframework/notary/client.test imports github.com/theupdateframework/notary/server imports github.com/theupdateframework/notary/utils imports github.com/spf13/viper imports github.com/spf13/afero imports github.com/spf13/afero/mem loaded from github.com/spf13/afero@v1.1.2, but go 1.16 would select v1.2.2 To upgrade to the versions selected by go 1.16: go mod tidy -go=1.16 && go mod tidy -go=1.17 If reproducibility with go 1.16 is not needed: go mod tidy -compat=1.17 For other options, see: https://golang.org/doc/modules/pruning Signed-off-by: Sebastiaan van Stijn <github@gone.nl> |
||
---|---|---|
.. | ||
.travis.yml | ||
CHANGELOG.md | ||
LICENSE | ||
README.md | ||
decode_hooks.go | ||
error.go | ||
mapstructure.go |
README.md
mapstructure
mapstructure is a Go library for decoding generic map values to structures and vice versa, while providing helpful error handling.
This library is most useful when decoding values from some data stream (JSON,
Gob, etc.) where you don't quite know the structure of the underlying data
until you read a part of it. You can therefore read a map[string]interface{}
and use this library to decode it into the proper underlying native Go
structure.
Installation
Standard go get
:
$ go get github.com/mitchellh/mapstructure
Usage & Example
For usage and examples see the Godoc.
The Decode
function has examples associated with it there.
But Why?!
Go offers fantastic standard libraries for decoding formats such as JSON. The standard method is to have a struct pre-created, and populate that struct from the bytes of the encoded format. This is great, but the problem is if you have configuration or an encoding that changes slightly depending on specific fields. For example, consider this JSON:
{
"type": "person",
"name": "Mitchell"
}
Perhaps we can't populate a specific structure without first reading
the "type" field from the JSON. We could always do two passes over the
decoding of the JSON (reading the "type" first, and the rest later).
However, it is much simpler to just decode this into a map[string]interface{}
structure, read the "type" key, then use something like this library
to decode it into the proper structure.