refactor(meal-plan) Use NameInputDialog for creating and renaming meal plans #50
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "meal-plan-name-input-dialog"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The meal plan's create and rename dialogs become the shared
NameInputDialog, so the app has one single-field name dialog instead of three. Follow-up from plan 001, D8.Depends on #47 (shopping lists), which introduces
NameInputDialog. This branch is stacked on001-shopping-lists, so until #47 is merged the diff here also shows all of #47; the only change of its own is the last commit (f49a258). TheWIP:prefix blocks merging until #47 is in; then this branch gets rebased ontostageand the prefix removed.Changes
MealPlanPagerendersNameInputDialogfor create and rename, with the meal plan's own texts ("Neuen Essensplan erstellen", placeholder "z. B. Woche 23", "Umbenennen").MealPlanCreateDialog.tsxandMealPlanRenameDialog.tsxare deleted.docs/architecture.mdand theNameInputDialogdoc comment are updated.Behaviour is unchanged: trimmed name, empty name can't be confirmed, rename disabled while unchanged. The only visible difference: the field uses
text-baseon phones, which keeps iOS from zooming into it.Verification
npm run build,npm run lint(only the 2 existing warnings inMealPlanDayProvider) andnpm run test(368 tests) pass./verify-uiasuser: create a plan (empty name disabled, Enter creates), rename it (prefilled, disabled while unchanged), the dialog fits on all five viewports; the test plan was deleted afterwards.🤖 Generated with Claude Code
WIP: refactor(meal-plan) Use NameInputDialog for creating and renaming meal plansto refactor(meal-plan) Use NameInputDialog for creating and renaming meal plans