From a099c87500f0205b6445001c0e5b8346713a23bb Mon Sep 17 00:00:00 2001
From: Michael Genson <71845777+michael-genson@users.noreply.github.com>
Date: Fri, 18 Jul 2025 21:20:02 +0000
Subject: [PATCH] fix timezone bug in recipe mealplan dialog

---
 frontend/components/Domain/Recipe/RecipeContextMenu.vue | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/frontend/components/Domain/Recipe/RecipeContextMenu.vue b/frontend/components/Domain/Recipe/RecipeContextMenu.vue
index 1a034d065..acf44b7a2 100644
--- a/frontend/components/Domain/Recipe/RecipeContextMenu.vue
+++ b/frontend/components/Domain/Recipe/RecipeContextMenu.vue
@@ -269,13 +269,17 @@ export default defineNuxtComponent({
       recipeName: props.name,
       loading: false,
       menuItems: [] as ContextMenuItem[],
-      newMealdate: new Date(Date.now() - new Date().getTimezoneOffset() * 60000),
+      newMealdate: new Date(),
       newMealType: "dinner" as PlanEntryType,
       pickerMenu: false,
     });
 
     const newMealdateString = computed(() => {
-      return state.newMealdate.toISOString().substring(0, 10);
+      // Format the date to YYYY-MM-DD in the same timezone as newMealdate
+      const year = state.newMealdate.getFullYear();
+      const month = String(state.newMealdate.getMonth() + 1).padStart(2, '0');
+      const day = String(state.newMealdate.getDate()).padStart(2, '0');
+      return `${year}-${month}-${day}`;
     });
 
     const i18n = useI18n();