#w7d2

I ran for 30 minutes straight!

W7D2, where the run is 25 minutes but I kept on going just to see if I could do an extra five minutes since the runs in week 9 are all 30-min runs.

Bish I DID it!

My speed on the treadmill was 5.0, which is hella slow, but it keeps me from feeling worn out.

Can I talk about Lush Toothy Tabs?

I have been low key nauseated since the beginning of the pregnancy, but it is getting worse and lasts longer throughout the day.

Today I Learned: about Stores in React

We began the day by reviewing the previous day's project. After review, we had a lecture regarding the use of 'Stores' with React.

In React, stores contain the app's state and logic. Stores manage the state of various objects. In addition to storing data, stores register callbacks to invoke when the state of the store changes to alter the UI.

Today was our second day with React and our first day integrating React with Rails.

Rather than rending React elements with hard-coded props and state today, we instead built stores for each model in our Rails app from which React components could acquire state. Then, our topmost component could pass down props to its children based on that state, allowing our whole React frontend to dynamically reflect the state of our entire app.

To achieve this, we gave our stores a fetch method that would fetch all of the objects of its type from an API that we wrote for that type using a Rails controller. Furthermore, this fetch method would trigger a call to any "handle change" callbacks that our React components added to our store when those components mounted. In these callbacks, our components would update their state based on the new state of the store, thereby causing them to re-render if their state changed based on the newly acquired data in the store. In this way, we ensured that nothing would change in our store's data without that change being reflected in our components if that data is relevant to what those components should render.