marcuswolschon / shoppingfortandoor Goto Github PK

UrL = Model.apiUrl + "/../view/recipe/" + recipeId

e.g. "lunch" set to notify at 10:00, "dinner" for 16:00 and "breakfast" not at all

1. shown in "edit" for a single supermarket
2. explicitely describe that we misuse the description field here.
3. feature to be activated in settings first, so we don't always need a location

We currently only store the API credentials.
Storing downloaded foods, receipt-imaged. receipts, shopping lists,... was the plan all along.

1. store a single item as it's ID + Name + Description and a json string to be independent of future schema updates. (The data we deal with is tiny and we don't search for anything but an id and in lists we only show name+description)
2. store each supermarket from "/api/supermarket/"
3. store the entire shopping list from "/api/shopping-list-entry/"

1. Take recipe from shopping-list-entry->recipe_mealplan->recipe and ingredient from shopping-list-entry
2. Fetch "/api/recipe//" and cache in DB
3. Search all steps for all ingredients to find that ingredient ID
4. Take the field note
5. be prepared to find the ingredient multiple times with different notes

Android XML drawables work cross platform in JB-Compose.

Desktop: painterResource("ic_all_inbox.xml") in jvmMain/resources
Android: painterResource(R.drawable.ic_all_inbox) in src/main/resources/drawable/

Implementation should be similar to #24

• /api/meal-plan/
• highlight items needed today
• offer sorting by this new column

• use the new order of supermarket departments of "Shopping List V2" for sorting by department