Paul van Tilburg 014ca5a151 Handle errors on the API side ... * The map endpoints return an HTTP 404 error in case of unknown or out-of-bound locations * The forecast endpoint with an address returns an HTTP 404 with error JSON in case geocoding fails * The forecast endpoints return the errors per metric in the `errors` field of the forecast * Implement `Display` for `Metric` * Use a `BTreeMap` to have an ordered `errors` field/object * Also log the errors to the console * Update the tests * Document the errors that can occur		2022-06-06 16:46:52 +02:00
..
providers	Introduce error types, switch to Results everywhere	2022-06-06 15:37:54 +02:00
forecast.rs	Handle errors on the API side	2022-06-06 16:46:52 +02:00
lib.rs	Handle errors on the API side	2022-06-06 16:46:52 +02:00
main.rs	Run map refresher as an ad hoc liftoff fairing	2022-06-05 21:25:56 +02:00
maps.rs	Log errors of the map refresher task separately	2022-06-06 15:38:38 +02:00
position.rs	Introduce error types, switch to Results everywhere	2022-06-06 15:37:54 +02:00
providers.rs	Add the combined provider	2022-02-24 20:40:07 +01:00