- This EventTrackerProject tracks workouts so weight, reps, and sets of exercises can be recorded to track growth. This project started out as a single HTML page that was dynamically changed via Javascript DOM manipulation and XHR to send and receive JSON Objects from RESTful api's. Over the course of this project the decision was made to change the front end to angular. This entire website is still a dynamic single page application but the data manipulation is accomplished through data-binding and DOM manipulation is offloaded to angualar. the logic that was offloaded by using Angular did not end there though. Dependency injection and modularization helped to keep code clean and maintainable.
- Utilizing Components and services on the front end help keep the entire stack within the MVC framework, and separate concerns.
- An insturmental peice and one of my favorite parts of the angular part of this application was utilizing pipes to filter the data. Because of the one to many relationship within the database actually removing data from the database is a fairly strenuous activity. However, to get around this each row has a column enabled and this is how checking is done to determine whether or not a peice of data should be displayed. Instead of having to make this check every time data is displayed, I was able to use a pipe that filters the data as soon as it gets populated from JSON.
- One thing I learned on this project which will be helpful in the future was how to pass data between child and parent components. It was necessary to two-way bind and one-way bind data in different components and had it not been for this functionality it would not have been possible to separate concerns through different components.
- Stylings are handled utilizing Bootstrap and CSS.
- The Api's are handled via a Java backend utilizing Spring Boot and JPA. The underlying Database is a MySQL database and communication with the database is handled using Hibernate in conjunction with JPA. With this app there are full CRUD operations on on two database tables representing Workouts and exercises.
| Java | Javascript |
| Angular | Typescript |
| JPQL | SQL |
| AWS | EC2 |
| Spring Boot | Spring Data JPA |
| REST | JSON |
| AJAX | XHR |
| Bootstrap | CSS |
| HTML | DOM |
| JUnit | TDD |
| Hibernate | JPA |
| Eclpise | Visual Studio Code |
- Importable postman collection at link above for a local instances only
| HTTP Verb | URI | Request Body | Response Body | Purpose |
|---|---|---|---|---|
| GET | http://54.201.168.70:8080/WorkoutTrackerBoot/api/workouts |
Collection all workouts | List or collection endpoint | |
| GET | http://54.201.168.70:8080/WorkoutTrackerBoot/api/workouts/1 |
Representation of workout 1 |
Retrieve endpoint | |
| POST | http://54.201.168.70:8080/WorkoutTrackerBoot/api/workouts |
Representation of a workout | Description of the result of the operation | Create endpoint |
| PUT | http://54.201.168.70:8080/WorkoutTrackerBoot/api/workouts |
Representation of a new version of workout 1 |
Replace endpoint | |
| PATCH | Not Allowed |
|||
| DELETE | http://54.201.168.70:8080/WorkoutTrackerBoot/api/workouts/1 |
Delete route changes enabled column to false in DB |
| HTTP Verb | URI | Request Body | Response Body | Purpose |
|---|---|---|---|---|
| GET | http://54.201.168.70:8080/WorkoutTrackerBoot/api/exercises |
Collection all exercises | List or collection endpoint | |
| GET | http://54.201.168.70:8080/WorkoutTrackerBoot/api/exercises/1 |
Representation of exercise 1 |
Retrieve endpoint | |
| POST | http://54.201.168.70:8080/WorkoutTrackerBoot/api/workouts/1/exercises |
Representation of a exercise | Description of the result of the operation | Create endpoint |
| PUT | http://54.201.168.70:8080/WorkoutTrackerBoot/api/exercises |
Representation of a new version of exercise 1 |
Replace endpoint | |
| PATCH | Not Allowed |
|||
| DELETE | Not Allowed |
Add the ability to update and delete Exercises.- create a nav bar with several options to create workouts, search for workouts.
- show a limited veiw of workouts and load more as scrolling occurs.
- add more stylings with pretty graphics.
- Each exercise is its own entity in the DB and only associated with one workout. It would be better to be able to reference the same exercises in multiple workouts but due to limitations on Many To Many relationships from JPA there is not an elegant way to accomplish this.
- Every time page is loaded all the workouts stored in the db are loaded. This will not be optimal as the size of the DB grows.