Anton Kaliaev 65a07b80a3 change logger interface to not return errors (Refs #50) ... See https://github.com/go-kit/kit/issues/164 for discussion of why kitlog returns an error. ``` Package log is designed to be used for more than simple application info/warning/error logging; it's suitable for log-structured data in an e.g. Lambda architecture, where each invocation is important. I agree with you that if we were doing only application logging the error would be more noise than signal. But the scope of the package is larger than that. ``` Since we are doing only application logging and we're not checking errors, it is safe to get rid them.		2017-09-20 02:49:51 -04:00
..
filter.go	change logger interface to not return errors (Refs #50)	2017-09-20 02:49:51 -04:00
filter_test.go	change logger interface to not return errors (Refs #50)	2017-09-20 02:49:51 -04:00
logger.go	change logger interface to not return errors (Refs #50)	2017-09-20 02:49:51 -04:00
nop_logger.go	change logger interface to not return errors (Refs #50)	2017-09-20 02:49:51 -04:00
testing_logger.go	[log] allow for custom color funcs	2017-05-14 12:03:45 +02:00
tm_json_logger.go	filter	2017-05-05 21:48:03 +04:00
tm_logger.go	change logger interface to not return errors (Refs #50)	2017-09-20 02:49:51 -04:00
tm_logger_test.go	change logger interface to not return errors (Refs #50)	2017-09-20 02:49:51 -04:00
tmfmt_logger.go	[log] add separator	2017-05-12 17:39:00 +02:00
tmfmt_logger_test.go	squash module key if multiple keyvals were provided	2017-05-08 17:30:21 +04:00
tracing_logger.go	change logger interface to not return errors (Refs #50)	2017-09-20 02:49:51 -04:00
tracing_logger_test.go	[log] tracing logger	2017-05-23 23:06:20 +02:00