-
The easiest scenario on hop example (the same works for any ingredient that impacts beer parameter calculations):
1. add some hop item to the recipe, it will get added with 0,0 mass amount
2. change…
-
Description: #32
Depends on: #19
-
There needs to be a form to fill in the blanks to save information about a custom beer recipe. This form will let you create a new recipe or edit an existing one. This form will locally save to the ph…
-
Add different ingredients from a list.
~~Automatically build beerxml file.~~
ollej updated
7 years ago
-
Currently JSON schema converted from XSD contains multiple repeated keys, for instance `Fermentables` can contain multiple instances of `Fermentable`. This might be ok for JSON, but cannot be easily d…
-
Root JSON schema defines an object with these required (!) properties:
* version
* fermentables
* miscellaneous_ingredients
* hop_varieties
* cultures
* profiles
* styles
* procedure
* recipe…
-
The styles, yeast, yeast types, fermentables, fermentable types, hops, hop types all need an additional model built for them to store suggestions for each model.
For a yeast suggestion, the sugges…
-
All current references to "Efficiency" should be replaced by "Brewhouse Efficiency", and should be a required correction, with the conversion efficiency, lauter efficiency, and mash efficiency variabl…
-
The fermentable model needs refactoring as pointed out by some brewers on reddit. We need to be able to track who makes the fermentable, what year the data is from, as well as some additional values r…
-
Before the v2.x update the required info field captured both required and optional information for entries per the BJCP guidelines. We'd like to see a return to this functionality because having to tu…