Plan system ingredients concept

[johnnycopes]

OVERVIEW

Users shouldn't have to manually enter all their own ingredients from scratch. One way to help users is to have a default collection of common ingredients (likely several thousand) that can be offered to the user.

TECHNICAL PROPOSAL

The /ingredients collection will contain a mix of system and user ingredients. This is the proposed shape of each:

interface SystemIngredientDto {
  id: string;
  name: string;
  type: IngredientType;
}

interface IngredientDto {
  id: string;
  uid: string;
  name: string;
  type: IngredientType;
  dishIds: string[];
}

The most user-friendly way to add a new ingredient would be via a typeahead input in which suggested system ingredients are displayed to the user that match what they're typing. If the user chooses one of these new ingredients, a new user ingredient document is added to the database with the same name and type as the chosen system ingredient. This way, the user now has their own version of the ingredient that they can modify as normal.

[johnnycopes]

As explained here, this task is being removed from #302 as the scope has changed and this item is now a separate consideration