jpdillingham/swot

A web application for designing, tracking, and reporting progress on workouts. Written in JavaScript with React, Redux, Material UI, and hosted by a serverless AWS backend.

swot's Issues

Consider adding a hash or timestamp to records to prevent synchronization conflicts

Add a hash field or timestamp to records and check the value against the present database value when updating.

Combine front and backend projects

Use the Travis CI matrix feature (https://stackoverflow.com/questions/27644586/how-to-set-up-travis-ci-with-multiple-languages) to retail the existing build/deploy functionality.

Schedule Workout dialog validation does not reset when fields change

Repro:

• Open dialog
• Don't select a Routine, hit Save
• Observe validation error
• Select a Routine, or change date/time

Validation error should clear upon change of any of the fields, but does not.

Make app title dynamic; display name of current content

For example, when viewing Workouts, the app title should say "Workouts". This requires changes to AppContainer, an addition to AppReducer for current page title, and additions throughout routeable components to update the title upon load.

Add confirmation to Workout stop FAB

Implement propTypes

Disable user signups.

There's a risk of someone signing up and using the api to rack up charges.

• Disable user signups in Cognito
• Disable the "Register" functionality in the UI
• Add a message to contact administration to obtain an account

Calendar does not display load animation properly

Expected behavior is that a blank screen with a spinner is shown while initial calendar data is fetched. Actual behavior is that the calendar is displayed with the currently loaded Excercises, and the spinner is shown overlayed.

Suppress display of the Calendar component until the initial fetches are complete.

Alias Workouts history endpoint to Routines history

Conceptually they are the same thing, and adding the Exercise endpoint requires the addition to be semantically consistent.

Add ability to schedule Workouts from WorkoutsCalendar

Include the FAB and dialog from Workouts, and open and pre-populate the dialog on select of a calendar cell.

Implement an axios response interceptor to attempt to fetch a new access key on 401

Follow the interceptor pattern used in api.js and use ensureSession() and/or refreshSession() in SecurityActions.js to fetch the new key.

Improve display of Workout/Exercise notes on click within a report component

Implement WorkoutsHistory using the new History components

Implement a calendar page to display past and upcoming Workouts.

Include a Floating Action Button and the WorkoutsDialog component to allow for scheduling from this page.

Consider clickable calendar cells in lieu of a FAB; clicking a cell would open the WorkoutsDialog and pre-populate the date with the clicked date.

Implement progress indicator when starting/stopping Workouts or WorkoutExcersies.

Ensure the solution is consistent with WorkoutsHistory pagination and filtering.

Create Exercise report(s), similar to WorkoutsHistory.

Tabular View

• Display a table with columns for each metric in the data set (map and reduce)
• Map results to appropriate columns (columns as props, row factory? needs design)
• Ability to filter by exercise by passing id in route

Exercise metrics may change over time. Columns in the history table should be dynamic in that if an Exercise contains a metric, it should be displayed in a column. Exercises in the same data set lacking that metric will have a blank column or potentially N/A.

Add ability to adjust the time of a scheduled workout

Review API implementation among *Actions.js

Implementation differs slightly in ExercisesActions and RoutinesActions. Review and bring into alignment.

Also, test the downstream notification logic to ensure errors are displayed in a reasonable way. The following suggests that they aren't:

            this.props.deleteExercise(exercise)
            .then(response => {
                this.props.showSnackbar('Deleted Exercise \'' + exercise.name + '\'.')
                resolve(response);
            }, error => {
                let message = 'Error deleting Exercise'
                message += error.response ? ': ' + JSON.stringify(error.exercise.data).replace(/"/g, "") : '.'

                this.props.showSnackbar(message);
                reject(error);
            })

Is error.exercise.data correct? Doesn't seem like it would be.

Refactor backend to store completed Workouts in a separate DynamoDB table

Perhaps keyed on user id and Workout id. Investigate table scanning methods to determine the best way to implement. The goal is to support the scale of completed Workouts.

Create an Exercise progress report

Include a graph of metrics over time

Add ability to navigate to Workouts History from RoutineCard

Via a brief dialog, similar to ExerciseHistoryDialog.

Add logout confirmation dialog

Add an Exercise history dialog which can be opened from the ExerciseForm in the workout stepper.

The goal is to provide the user with a tabular history of the Exercise metrics.

Depending on design (space, etc) potentially incorporate a graph.

Convert WorkoutsHistory into a reusable History component

Retain common functionality, namely within Options:

• Start/end selection
• Order
• Pagination
• Parent-defined options (render on new row in header, append name/selection to filters)

Accept children props for rendering results, return filters via a callback so the parent can perform queries.

Review and align all api implementation. This is known to vary across Routines and Exercises specifically

Make enter/login/register button default/clickable by pressing enter within a field

Create a reports folder and move WorkoutsHistory components to it.

Add Exercise reports when they are built.

Implement endpoint to differentiate completed and incomplete (in progress + scheduled) Workouts. Allow for pagination.

• Input checking
• In Progress vs Completed
• Sorting
• Pagination
• Filtering by Routine
• Filtering by date range

Add API animation to login dialog

Display a spinner while the login API is invoked.

Workout sequence is not set properly for Routines with only one Exercise

This value should be zero but is undefined.

Navigating to base route when not logged in raises exceptions

Reproduce:

• Log out of the application
• Navigate to base url (without /login)
• Observe the exceptions above

It appears as though the default route is attempting to fetch details for the dashboard and getting the above errors, which is what causes the redirect to /login. The code needs to be updated to check for a valid session prior to requesting data or displaying components.

Configure progress chart colors and style

Place the configuration in a component or shared lib that can be used by both the ExerciseProgress and ExerciseProgressDialog components.

Add the ability to delete a Workout history record

Implement endpoint to retrieve Exercise history.

Follow the patterns used for Workout history. Data will need to be pulled from Workouts first, then exercises will need to be extracted and aggregated.

Review and align all snackbar notifications related to Workouts

Add History navigation to Exercise card

Refactor AppContainer to accept links as a prop

Instead of burying it inside the AppContainer component, expose it for visibility within the App component

Add History and Progress navigation to ExerciseForm

Presently, the FAB on ExerciseForm opens the History dialog. When the Progress dialog (#146) has been implemented, update this component to allow display of the History and Progress dialogs.

Ideas:

• Change the existing FAB to an info icon, and when clicked display two mini FABs for history and progress
• Open a menu when the FAB is clicked and display history and progress options
• Use a vertical dot menu for the history and progress options, and change the FAB to start/stop controls for the exercise (this is consistent with the rest of the app, but I'm not sure I like it here)

Responsive design

Presently certain components are restricted in width to display on mobile (Exercise/Routine cards, WorkoutExerciseForm)

Exercise/Routine should have a default width for desktop/large displays and should have responsive width on mobile/small displays

WorkoutExerciseForm can expand the entire width of the screen (similar to other Workout related components) but should have a responsive width for mobile/small displays

Implement input validation across backend api

Standardize reducer naming

Some reducers are plural, others are not. Pluralize all in name and filename.

Complete Workout confirmation dialog doesn't wait for API before closing

The dialog should remain open until a response is received, but presently does not.

Create Exercise progress report

Include a graph of metrics over time

Implement WorkoutReport component, to be shown after completing a Workout or when drilling down from WorkoutsHistory.

Add Progress navigation to Exercise history dialog

Perhaps add tabs to show tabular/graph in the dialog, and add buttons to navigate to full versions.

Implement endpoint to retrieve Routine history.

Refactor toggleable notes into a shared component

Add a history dialog for Workouts

See ExerciseHistoryDialog. Include list of dates.

Split backend into multiple files

Divide by domain object (Workout, Routine, etc).

• Create utility.js for shared functions (getUser)
• Determine folder structure (if any)
• Copy existing functions to new files, then stub routes in index (e.g. app.get('/exercises', exercises.get))

Add Progress dialog

Similar to the History dialog, provide a truncated version of the Progress page.