drazhar / trainings-log Goto Github PK

While logging a workout, the data entries got messed up on saving.

It seems like the value of one field was applied to all values.

On the database, if you add a weight with the same date, the old value gets overwritten, which is intended.
At redux it's simply added to the object. If a date already exists, it should be overwritten.

At the calendar or timeline overview it should be possible to copy an workout to repeat it.

When copied, only the workouts and the amount of sets should be copied. The placeholder values should still be filled with the most recent references as it should be done with #14.

Punkte in der Chart View Übersicht: Farbig für trainiert und grau für Ruhetag.

The animation of the dots is off because the association which dot is for what entry is most likely based on the date. This entry changes if the axis is moved. The association should be based on the index in the array.

The charts should be ordered by the last entry date so the newest are at the top.

When an exercise is added to a workout, the entered data is moved incorrectly. This is most likely because the new div is added at the top.

I think it would also be better to add the div at the bottom again and automatically scroll the screen down. The add exercise button und timer will be placed relative to the screen anyway at the later design.

Describe in the readme how to setup the database:
[] Docker commands
[] database.dump file for some base data
[] Dummy docker-compose file

Often times when you open the weight view, the weight input won't get prefilled.

Das Gewichtsfeld soll standardmäßig ausgefüllt werden mit dem nächsten eingetragen Gewicht.

Linear Unterpolieren?

Type ändern damit man +/- klicken kann oder ein Dropdown wo man auch eintragen kann.

When a new exercise is added at the workout form, the log values from the exercise last time should be added as placeholders

During logging a workout, it's possible to enter no value at an exercise. This messes up some entries in the database. It should be checked during the submission.

Instead of giving the user the flexibility and therefore increased complexity, the colors to choose from should be pre defined.
With this it's also possible to define different shades for dark and light mode and also secondary colors for possibly multiple information in one chart.

Currently there are two functions, one for getExercises and one for getWorkout. In most cases both are needed so it would make sense to merge the two. This would reduce the overhead data of the HTML headers and improve performance. The only downside would be, that the fetching could take a bit longer and in some rare cases, some unnecessary data is queued from the database.

It would make it also easier to calculate the data for the charts, exercise order and exercise dummy data.

shouldn't be a nan or similar

Aktuell wird das Diagramm ständig komplett erneuert. Eigentlich sollte das Diagramm nur beim Laden erstellt werden und bei Updates nur aktualisiert werden.

Beim Eintragen soll der Wert direkt angezeigt werden und aus dem Input Feld verschwinden.

Lösung überlegen wie man komfortabel eine Benachrichtigung an Benutzer schicken kann, zum Beispiel wenn etwas falsches eingetragen wurde oder keine Daten verfügbar sind.

The circled which idendicate even trained on a day should be multi colored like the exercises done to give a better overview what was done.

Instead of a simple list of all the data entries, these should be grouped by year and month. Also the year and Month could have some statistics like weight gain/lost.

Beim Eintragen von einem neuen Workout wird dieses sauber in der Datenbank gespeichert, aber das Workout Objekt in Redux wird nicht sortiert was zu falschen Diagrammen führt.

Maybe use Syncthing on the Raspberry as a container to backup the database to the Laptop.

First issue:

User permissions change automatically after docker-compose up. This makes it difficult to backup the data.