distribution/vendor/github.com/mitchellh/mapstructure
Sebastiaan van Stijn 6e8dd268a8
update to go 1.18 (continue testing against 1.17)
Go 1.16 reached end of life, so update to the current version of Go, but also
run CI on the previous version (which is still supported).

We should probably also decide wether or not we want the Dockerfiles to pin to
a specific minor version; this makes the releases more deterministic.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2022-05-05 10:36:28 +02:00
..
.travis.yml update the golang compiler version and the versions of several dependencies 2019-06-19 22:43:52 -07:00
CHANGELOG.md update the golang compiler version and the versions of several dependencies 2019-06-19 22:43:52 -07:00
decode_hooks.go update the golang compiler version and the versions of several dependencies 2019-06-19 22:43:52 -07:00
error.go Move to vendor 2016-03-22 10:45:49 -07:00
LICENSE Move to vendor 2016-03-22 10:45:49 -07:00
mapstructure.go update the golang compiler version and the versions of several dependencies 2019-06-19 22:43:52 -07:00
README.md update the golang compiler version and the versions of several dependencies 2019-06-19 22:43:52 -07:00

mapstructure Godoc

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.