The data is saved. This was verified by clicking save on the form and refreshing the page.

This will be a breaking change. A conversion tool must be provided to change the form of the data. The tool must not change the data in place, but create a new database with the transformed data.

On the brew page, show the user one form at the top that replaces the three forms for "Brew Note", "Fermentation Note", and "Tasting Note". The single form should contain the following:

Text field: Note type
Textarea: Note contents

Each note must continue to have a timestamp.

Data structure:

{ time: 'ISO-8601 date', type: 'brew', text: 'Contents of the note' }

The list of notes at the bottom of the brew page will also need to be updated. Use the type to create sections for each unique type and list all notes of that type in descending chronological order. For example, given three notes as follows:

[
  { time: '2020-02-02T12:00:00z', type: 'Brew', text: 'brew 1' },
  { time: '2020-02-02T13:00:00z', type: 'Observation', text: 'observation' },
  { time: '2020-02-02T14:00:00z', type: 'Brew', text: 'brew 2' }
]

The following should be rendered:

Brew
2020-02-02 @ 12:00:00
brew1

2020-02-02 @ 14:00:00
brew 2

Observation
2020-02-02 @ 13:00:00

I use a refractometer to measure how much sugar is in my wort before and after fermentation to understand how much alcohol is in the beer. After some reading, it seems that measuring using the Brix scale on my device will be the most accurate. Using the original and final brix reading, ABV can be calculated. However, the alcohol present in the final brix reading skews the refractometer's reading. Using the following algorithms, ABV can be calculated taking into account the correction for the refractometer.

Calculating ABV

Terms

• OB: Original Brix reading before fermentation
• FB: Final Brix reading after fermentation
• FG: Final Gravity
• ABW: Alcohol by Weight
• ABV: Alcohol by Volume

Algorithm

const OB = 12;
const FB = 6;
const FG = 1 + (-0.002349 * OB) + (0.006276 * FB);
const ABW = (0.67062 * OB) - (0.66091 * FB);
const ABV = (FG * ABW) / 0.791;

References

• Article published by Petr Novotný on calculating gravity and ABV of beer using a refractometer
• Wikipedia article on ABW and ABV

As a user
When I start typing in the note type field on the brew page
I want to see a list of note types I've already used on this brew and have the ability to select one of them

As a user
I want to brew the same recipe multiple times
So I can track how different brew days produce different results on the same recipe

This will be a breaking change. A tool must be provided to migrate brews in a v1 database to the new structure. The tool must not modify the original database.

• The index page must be updated to show a list of recipes
• The recipe page must have an action to start a new brew day
• The recipe page must list the brews that have been started using that recipe
• The brew page must display the recipe so it's easy to work through a brew day without leaving that page
• The brew page must allow a user to add a note
• The brew page must display the notes on that brew

If a user or users have the same recipe of brew open at the same time, make different changes, and both commit, the document will be updated with the second user's changes losing the changes from the first user. Adding a field to each document that contains a revision identifier and checking that the document in the database is the same revision before committing the changes will prevent overwrites.

Definition of Done

• Each recipe and brew document must contain a new field named _version that contains a integer that is incremented when a change is made to the document
• When saving a document, a new check must be in place that verifies the _version in the document being changed is the same as the revision in the database
• If the _version is not the same, the server must respond with a 400 http status code with the text "DOCUMENT_OUT_OF_DATE" and include the latest version of the document from the database
• If the client receives a status of 400 with status text "DOCUMENT_OUT_OF_DATE", the client should use the object returned with the 400, make the changes requested by the user, and re-submit the PUT request

As a user
I want to be able to update a recipe
So that when I'm shopping for ingredients and find they are not available, I'm able to change the recipe on the fly

The recipe is available in two places: the recipe itself, and the copy of the recipe inside a brew when a new brew day is started. The system should allow editing the recipe in both places.

Time to start migrating to vue components. Let's start with the recipe view. It can be reused in both the recipe page and the brew page.