File: control

package info (click to toggle)
golang-github-mitchellh-mapstructure 1.3.3-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, bullseye, bullseye-proposed-updates, sid
  • size: 212 kB
  • sloc: makefile: 2
file content (45 lines) | stat: -rw-r--r-- 2,166 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Source: golang-github-mitchellh-mapstructure
Section: devel
Priority: optional
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Uploaders: Kouhei Maeda <mkouhei@palmtb.net>,
           Tianon Gravi <tianon@debian.org>,
           Anthony Fok <foka@debian.org>,
           Tim Potter <tpot@hpe.com>,
Build-Depends: debhelper-compat (= 13),
               dh-golang,
               golang-any,
Standards-Version: 4.5.0
Homepage: https://github.com/mitchellh/mapstructure
Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-github-mitchellh-mapstructure
Vcs-Git: https://salsa.debian.org/go-team/packages/golang-github-mitchellh-mapstructure.git
Rules-Requires-Root: no
Testsuite: autopkgtest-pkg-go
XS-Go-Import-Path: github.com/mitchellh/mapstructure

Package: golang-github-mitchellh-mapstructure-dev
Architecture: all
Depends: ${misc:Depends},
         ${shlibs:Depends},
Description: library for decoding generic map values into native Go structures
 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.
 .
 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.
 .
 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.