dseisun / nerdouts Goto Github PK

Right now the primary key is an autoincrementing value. This means however that if you try to move the database around, or reload the exercises they need to be loaded to have exactly the same key.

Proposed fix:
The key for the exercise table should be a short string like normal_pushups that would be stored in the exercise data if ever exported.

Sometimes I want a mix of a pre-generated exercise, but also I want to make sure I get exercise 'xyz' as well. Alternatively if I'm injured I may want to blacklist an exercise (or some category of exercise)

Python2 is finally really going EOL. We should migrate to python3

Currently it's just a passthrough of the "default_time" field in exercises. It should really be the total time for set (thus * 2 if it's for both sides)

Currently the default_time is the source of truth for how long an exercise took. This blocks us from being able to change the amount of time for an exercise, or having exercises with potentially dynamic times. There should be an exercise_time field on the workout_exercises association table that stores the actual amount of time spent.

Thinking of using black

When you whitelist an exercise it gets appended, but if it was going to be a part of the workout anyways you get duplicates. It should follow the expected behavior that all other workouts in that category get added before it re-add's an exercise

Which is where we snuck in some of the playlist bootstrapping which is now being skipped

Currently QA mode will happily write records as if they were prod. They should either write to a sandbox db, or should have a column set on the record that describes that these were test mode exercises

The dependency on clementine is obnoxious. It should be given a directory, or a playlist file (is there a standard?) and play the music directly from python

https://docs.python.org/2/distutils/setupscript.html

This'll help enforce some code organization as the project grows a bit

We're currently using the default logger, but it would be nice to be able to toggle between different logging levels (currently just using INFO for everything), and might be nice to have different formats for different parts of the application

Would be a lot easier if a user could just quickly spin up a sqlite db to test their work (or honestly even keep it long term)