mfrodl / myrmex Goto Github PK

Currently, only three exercise types are supported: jogging, yoga and weightlifting. This is obviously not enough for most users. On top of that, the existing implementation is not optimal because of code redundancy. If we wanted to add e.g. swimming, several files would have to be updated:

• models.py: new class
• views.py: all four methods would need at least one additional line of code
• calendar.html: new input field in form

A more universal solution would be to replace the three specific models with a generic one (Exercise) with additional fields type (a string) and units (also a string, preferably with pre-defined choices).

The form would then have to look a bit different too. Instead of a single input field, three would now be needed:

• <input> with <datalist> for exercise type
• <input type="number"> for quantity
• <select> (or <input> with <datalist>) for units

By default, only one row of input fields would be displayed, with a + button allowing the user to input additional entries, and a - button for removing the existing ones.

With this arbitrary exercise support, the fancy icons for jogging, yoga and weightlifting would not make sense anymore and could be removed from the application.

In order to avoid regressions, there should be an automated test suite executed after each commit.

Currently, the application is running in a single-user mode without any authentication. It would be convenient to allow multiple users to keep track of their individual exercise separately. The single-user functionality can be kept for demo purposes or discarded entirely.