We need to add a query to the interval Dao that will select unique intervals and alphabetizes them. I wrote a SQL query that should work.

SELECT DISTINCT i_name FROM interval ORDER BY i_name

I can't remember if we also wanted to add favorites to intervals but if we do, we can just add the sorting to the SQL query so we don't have to deal with it in kotlin

We currently have 0 integration tests so I decided to create an outline of all the things that need to be tested, and organized them by the screen they start on.

• Workout List Screen

  • Create workouts
    • Plus button opens modal
    • Input is validated
    • Cancel button closes modal
    • Add button adds a new workout and displays it
  • View workouts
    • Workouts are being displayed properly (proper formatting, favorite button is right)
  • Update workouts (TODO: Missing implementation)
  • Delete workouts
    • Swiping a workout removes it
    • Undo button re-inserts correctly

• Interval List Screen

  • Create intervals
    • Plus button opens modal (modal should be tested separately)
  • View intervals
    • Intervals are being displayed properly
  • Update intervals (TODO: Missing implementation)
  • Delete intervals
    • Swiping an interval removes it
    • Undo button re-inserts correctly (ORDER MATTERS)
  • Start button brings you to the timer screen

If you attempt to edit an interval, and then press the "add" button, it crashes due to a null pointer. The issue is on line 124 and seems to be related to how arguments are passed in.

I'm going off of Rylee's ER diagram from the project document for the entities, with the exception of the i_guid field on the workout entity because I don't think it makes sense for us to have a foreign key to a single interval on a workout. This is my plan for the Daos:

Workout:

• insert(vararg workout: Workout): Insert 1 or more workouts
• getAll(): LiveData<List<Workout>>: Retrieve all workouts from the database
• update(workout: Workout): Update a workout in the database (will update the entire row, not just changed properties)
• delete(workout: Workout): Delete a workout

Interval:

• insert(vararg interval: Interval): Insert an interval
• getByWorkout(workoutId: Int): LiveData<List<Interval>>: Retrieves all intervals for a specified workout
• update(interval: Interval): Update an interval
• delete(interval: Interval): Delete an interval

I didn't really see a reason to create queries for selecting a single workout or a single interval since I figure any time that we need the data from just one workout/interval we'll already have the data and just need to pass it around. Thoughts? Anything I missed?