yanic/data/response.go

package data

// ResponseData struct
type ResponseData struct {
	Nodeinfo   *Nodeinfo   `json:"nodeinfo" toml:"nodeinfo"`
	Statistics *Statistics `json:"statistics" toml:"statistics"`
	Neighbours *Neighbours `json:"neighbours" toml:"neighbours"`
	CustomFields map[string]interface{} `json:"-"`
}
Request all data types at once 2016-03-19 23:18:26 +01:00			`package data`

improve complete code with comments and co (thanks linter) 2017-01-20 22:27:44 +01:00			`// ResponseData struct`
Request all data types at once 2016-03-19 23:18:26 +01:00			`type ResponseData struct {`
[TASK] add respond(d) daemon - WIP 2019-01-24 02:54:21 +01:00			Nodeinfo *Nodeinfo `json:"nodeinfo" toml:"nodeinfo"`
			Statistics *Statistics `json:"statistics" toml:"statistics"`
			Neighbours *Neighbours `json:"neighbours" toml:"neighbours"`
add support for custom fields At the moment, if one has a custom respondd module which includes custom fields, Yanic will simply ignore these fields. Communities which have custom fields have to maintain patches on Yanic to have them available. This commit allows to define custom fields in the configuration file, which will cause Yanic to also save the values of these custom fields in its internal data structures. Output modules can then decide whether they want to include these fields. For most cases, this should avoid the need for patches in Yanic. 2019-11-17 10:44:11 +01:00			CustomFields map[string]interface{} `json:"-"`
Request all data types at once 2016-03-19 23:18:26 +01:00			`}`