Create a view model for the day details #161

savanni · 2024-01-20T20:16:08Z

savanni commented

2024-01-20 20:16:08 +00:00

I was having a lot of excess code dealing with handling data embedded into the middle of the view components. This got very complicated.

The view model holds all of the detail needed for DaySummary, DayDetail, and DayEdit, and manages the state of the data within the model. Then, when it's time to save data, it handles all of the details of committing the updated records to the database.

This PR also gets made much larger with a lot of linting fixes.

I was having a lot of excess code dealing with handling data embedded into the middle of the view components. This got very complicated. The view model holds all of the detail needed for DaySummary, DayDetail, and DayEdit, and manages the state of the data within the model. Then, when it's time to save data, it handles all of the details of committing the updated records to the database. This PR also gets made much larger with a lot of linting fixes.

savanni added 3 commits 2024-01-20 20:16:08 +00:00

18e7e4fe2f Start setting up the day detail view model

I've created the view model and added a getter function for the weight.
I'm passing the view model now to the DayDetailView, DayDetail, and
DayEdit.

I'm starting to set up the Save function for the view model, draining
all of the updated records and saving them.

None of the components yet save any updates to the view model, so
updated_records is always going to be empty until I figure that out.

1fe318068b Set up a view model for the day detail view

9bedb7a76c Tons of linting and get tests running again

savanni merged commit 9bedb7a76c into main

2024-01-20 20:17:27 +00:00

savanni deleted branch fitnesstrax/detail-view-model

2024-01-20 20:17:27 +00:00

Sign in to join this conversation.

No reviewers