Diary and Targets

[AustinGrey]

Now that we can add ingredients and recipes, it's time to add an interface for the diary and targets areas of the website. Emphasis should be on getting to the diary and adding what you ate as fast and with as little fuss as possible.

Targets should be another comprehensive manager (it is yet unclear, are these supposed to be something that evolves over time, or is the latest target the gold standard and that's that, past targets get ignored?)

[AustinGrey]

It seems that only one target is ever considered the 'current target', and it should be an error to create more than one, but the current system will use the first one it finds (which one is first is still undefined behaviour).

While working on the branch 8-diary-and-targets, I built a rudimentary diary that showed a bar chart indicating how the targets had been met so far and how adding a new food would alter the targets thus far. I built out some of the diary backend to support it and dealt with chart.js for the bar chart. Main challenges were dealing with how the server is expected to be in Australian time rather than UTC, and the balance between users adding food quickly, and discovering foods to add. I then had to place this project to the side as the pandemic and other matters took too much of my time. When I returned some of the components seemed cludgy

• Tagify and Autocomplete seemed useful for adding known food quickly, but useless if adding a new food.
• The bar chart idea is a great visualization, but overkill in terms of setup, and insufficient in terms of mobile friendliness and clarity.

Additionally I've been doing extensive work with Vue 2 and am finding that lots of the effort I put into creating custom html components, deliberately avoiding jQuery, and making my JS modular brought me to conclude that Vue would reduce the effort it took to create new features, while increasing reuse and modular design. As such I undertook to convert my existing code to Vue, in 2 days I was able to completely divorce the front end from the backend, hit feature parity, and got SPA routing for free. All on branch na-vue-experiments.

From here the target manager came together in just over a day. I may rename the branch to 8-vue-diary-targets as this should be the way moving forward.

I now need to turn my attention back to the diary. Dylan's micro bar stacks he built in django to show target levels in the diary may be the better option here compared to a bar chart, and could be improved now that Vue is in the equation.

[AustinGrey]

A pull request for this is in.