Branches - Paige & Caroline

[stupendousC]

Video Store Consumer

Congratulations! You're submitting your assignment!

Comprehension Questions

Question	Answer
Paste a link to the PR for your API	Ada-C12/video-store-consumer-api#14
For each person in your pair, describe something you learned from your partner during this project	Caroline learned from Paige: incorporating lifecycle methods to solve page load issues. Paige learned from Caroline: using Helpers.js to carry in fcns that's needed across diff component files
What was one area of React you gained more clarity on during this assignment?	How frontend and backend are related, and how they share info via API calls.
Describe how you solved the problem of having lists of movies that look mostly the same but have different content	Not sure what you mean, but the movies still retain their external_id's from whence they came.
Describe how you handled rentals with React	We made a new component, which contains the array of overdueRentals from the API call at first. Later we also added allRentals from a new API endpoint we made. When user clicks on the Rentals route, they'll see the default view of allRentals in a table, but they can toggle between seeing allRentals or overdueRentals.
Describe a DOM event your application handled	In the Customers component showing customers list, if the user clicks on the "SELECT" button next to a specific customer, it will send that customer's info up to App.js. App.js then sets state for CurrCustomer with that person's info, which then displays on the page.
Did you use any functional stateless components? What for?	We did at first, but because we wanted to use lifecycle methods, we had to change all our functional components to classical components
Did you use any container components? What for?	Per css-tricks.com: Container Components are almost always the parents of Presentational Components. In a way, they serve as a intermediary between Presentational Components and the rest of the application. They’re also called “smart” components because they’re aware of the application as a whole. So App.js is a container component. Because it contains all the important state info, and passes the relevant props down to its child components.
Do you have any recommendations on how we could improve this project for the next cohort?	Maybe a tutorial on how to deploy? We encountered problems because AWS didn't like the ruby language versions we used.