luet/vendor/github.com/mitchellh/mapstructure
Itxaka 4adc0dc9b9
Use goreleaser to build and release (#244)
Instead of using gox on one side and an action to release, we can merge
them together with goreleaser which will build for extra targets (arm,
mips if needed in the future) and it also takes care of creating
checksums, a source archive, and a changelog and creating a release with
all the artifacts.

All binaries should respect the old naming convention, so any scripts
out there should still work.

Signed-off-by: Itxaka <igarcia@suse.com>
2021-08-11 08:30:55 +02:00
..
CHANGELOG.md Use goreleaser to build and release (#244) 2021-08-11 08:30:55 +02:00
decode_hooks.go Use goreleaser to build and release (#244) 2021-08-11 08:30:55 +02:00
error.go Update vendor/ 2019-10-31 12:38:58 +01:00
go.mod Use goreleaser to build and release (#244) 2021-08-11 08:30:55 +02:00
LICENSE Update vendor/ 2019-10-31 12:38:58 +01:00
mapstructure.go Use goreleaser to build and release (#244) 2021-08-11 08:30:55 +02:00
README.md Update vendor/ 2019-10-31 12:38:58 +01: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.