influxdb/notification/endpoint
Johnny Steenbergen 86a359f34b chore(http): refactor http layer to be able to encode/decode influxdb.ID's safely
noticed that I had not used the http server as the entry point for server tests.
This was work to make that happen. Along the way, found a bunch of issues I hadn't
seen before 🤦. There are a number of changes tucked away inside the
other types, that make it possible to encode/decode a type with zero value for
influxdb.ID.
2019-12-13 09:46:01 -08:00
..
endpoint.go chore(http): refactor http layer to be able to encode/decode influxdb.ID's safely 2019-12-13 09:46:01 -08:00
endpoint_test.go chore(http): refactor http layer to be able to encode/decode influxdb.ID's safely 2019-12-13 09:46:01 -08:00
http.go chore(http): refactor http layer to be able to encode/decode influxdb.ID's safely 2019-12-13 09:46:01 -08:00
pagerduty.go chore(http): refactor http layer to be able to encode/decode influxdb.ID's safely 2019-12-13 09:46:01 -08:00
slack.go chore(http): refactor http layer to be able to encode/decode influxdb.ID's safely 2019-12-13 09:46:01 -08:00