| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Otherwise this is confusing.
|
|
It is always the same:
- amount float32
- unit string
- type string
This is good as a starting point. Later the types of ingredients might
have to be tracked. In this a string as key is maybe not the best.
|
|
This reduces the number of clicks to delete a recipe.
|
|
|
|
|
|
|
|
|
|
Using a database is way more complex (see the commit statistics of this
commit) than using files to store recipe data. Also administration and
usage is simpler.
|
|
|
|
The upstream URL can be encoded easily by the user in the Markdown-based
description. The title can be parsed by the first found top-level
heading in the Markdown text.
Thus these two columns are no longer used. To avoid an additional
migration they will be kept in the database.
|
|
Recipe images are currently complicated to implement and have little
use. Probably they will not be covered in the next release.
|
|
|
|
|
|
This reduces copies of the same HTML code.
|
|
Recipes should be completely editable and removable. Thus this edit page
was added.
|
|
This makes it easier to maintain and it looks better.
|
|
|
