mattermost/vendor/github.com/mitchellh/mapstructure
Agniva De Sarker 03a55367d9
MM-24312: Fix Dependency updates (#14391)
Automatic Merge
2020-04-29 14:06:09 -07:00
..
.travis.yml MM-24312: Fix Dependency updates (#14391) 2020-04-29 14:06:09 -07:00
CHANGELOG.md MM-24312: Fix Dependency updates (#14391) 2020-04-29 14:06:09 -07:00
decode_hooks.go Updating dependencies. 2018-12-05 13:51:47 -08:00
error.go PLT-6076 Adding viper libs for config file changes (#5871) 2017-03-25 03:31:34 -03:00
go.mod MM-24312: Fix Dependency updates (#14391) 2020-04-29 14:06:09 -07:00
LICENSE PLT-6076 Adding viper libs for config file changes (#5871) 2017-03-25 03:31:34 -03:00
mapstructure.go MM-24312: Fix Dependency updates (#14391) 2020-04-29 14:06:09 -07:00
README.md Upgrading server dependancies (#8308) 2018-02-16 09:47:51 -05: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.