chrisfleming/masscatering

An assistant for working out big shops

masscatering's Issues

Add Verbose minimal terminal output

Argument Parsing for Verbose or minimal terminal output

shopping list quantities in pre-defined units

Allow for food.yaml to refine units to present ingredients in the shopping list, but maintain the original units in the recipe.

Proposal for refactor of Menu YAML file

This issue is to discuss the proposal of a new YAML file structure, to facilitate

• Easy to present menu overview
• allow adding notes section to individual recipes
• allow adding no_print flag to menu items
• allow for menu ordering to take place

The current example menu YAML file structure is:

recipe_1:
      day_1:  num_people
      day_2: num_people
recipe_2:
      day_1:  num_people
      day_2: num_people
...

New proposed example structure

day_1:
      meal_1:  
            recipe_1: num_people
                  notes: Note to show at bottom of markdown recipe file
            recipe_2: num_people
            recipe_3: num_people
                  no_print: True
      meal_2:  
            recipe_1: num_people
                  notes: Note to show at bottom of markdown recipe file
            recipe_4: num_people
                  notes: Note to show at bottom of markdown recipe file
            recipe_5: num_people
...

The ability to add notes to a specific recipe will increase the flexibility for one-off recipe changes (ie. Make mash potato vegan) rather than having to create many copies of very similar recipes.

The no-print value is not required, but may save producing a .md file for generic items ie. generic hostel list, or per-person per day items.

Thoughts and opinions welcome

Updated post 2024 hostelling

Things that were needed

• More meat haggis (back to prev quantity)
• 2 sausages per kids for Toad
• More eggs for French Toast
• 2 Slices per person
• Oil for French Toast
• Double the fruit compote for french toast
• Dessert fruit with custard
• No kids Yoghurt

Refactor to use pint expression parsing for all unit value identification

pint expression parsing will parse strings, extract the units and values, and perform the unit combinations itself

This is instead of using "amount_units" function - as expect the pint project regex to be more effective than a small function written here

More potato with haggis

Think we did 7ish kg in the end?

Menu quantity items clash with recipe names

Direct menu item names currently collide with recipe names, and cause crash.

eg. in menu
rice: 1kg

This will cause crash as line 150 -153 will cause it to read recipe, rather than parse as ingredient directly.

Move unit registry to separate definition file

Move unit registry to separate definition file,

Using
>>> ureg.load_definitions('/your/path/to/my_def.txt')