yanic/respond
nrbffs 1a1163aaa1 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-12-29 15:41:05 +01:00
..
testdata Fix handling of compressed data 2016-03-19 15:07:44 +01:00
collector.go add support for custom fields 2019-12-29 15:41:05 +01:00
collector_test.go add support for custom fields 2019-12-29 15:41:05 +01:00
config.go add support for custom fields 2019-12-29 15:41:05 +01:00
config_test.go [TASK] handle domain_code (with filters) (#119) 2018-05-05 23:28:46 +02:00
respond.go [TASK] change default listing address to ff05::2:1001 2019-05-03 17:35:15 +02:00