Make end_date optional for hourly energy usage route

ClementNerma · Dec 1, 2024 · aec120f · aec120f
1 parent cc998c7
commit aec120f
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 3 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/Cargo.toml b/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "tapo-rest"
-version = "0.2.0"
+version = "0.2.1"
 edition = "2021"
 
 [dependencies]

diff --git a/src/server/actions.rs b/src/server/actions.rs
@@ -325,7 +325,9 @@ routes! {
             Ok(Json(client.get_energy_usage().await?))
         }
 
-        async fn get_hourly_energy_data(&state, &client, start_date: NaiveDate, end_date: NaiveDate) -> Json<EnergyDataResult> {
+        async fn get_hourly_energy_data(&state, &client, start_date: NaiveDate, end_date: Option<NaiveDate>) -> Json<EnergyDataResult> {
+            let end_date = end_date.unwrap_or(start_date);
+
             Ok(Json(client.get_energy_data(EnergyDataInterval::Hourly { start_date, end_date }).await?))
         }