Sammi-Jo and Jackie's Webflix and Chill

[jfahmy]

Video Store Consumer

Congratulations! You're submitting your assignment!

Comprehension Questions

Question	Answer
Paste a link to the PR for your API	Ada-C10/VideoStoreConsumer-API#15
For each person in your pair, describe something you learned from your partner during this project	Jackie - You can always use a button the user clicks instead of trying to lift up state/ if you designed something not the best way you can make it seem intentional. Sammi-Jo - If a higher component is storing the needed state then the child can probably be functional.
What was one area of React you gained more clarity on during this assignment?	All the CSS files get combined together into a single blob and will overwrite each other. SJ - ditto Jackie that the CSS files are just for organization, and to work around CSS class naming collisions, make CSS classes more specific to select the element you actually mean to select.
Describe how you solved the problem of having lists of movies that look mostly the same but have different content	We gave the list names explicit variable names and they had their own components and functionality. In the website display they live on separate pages so we didn't have an issue.
Describe how you handled rentals with React	The parent element stored "selectedCustomer" and "selectedMovie" as state and passed it to a child element called CheckOutForm.
Describe a DOM event your application handled	Anytime we changed state, either related to a movie list or to create a checkout, this created a DOM event.
Did you use any functional stateless components? What for?	Many of our lower-level components are functional because they are rendering a list item where the list will change in a higher-level class component. (For example, Customer and MovieCard.)
Did you use any container components? What for?	Yes, many parent components (such as AppRouter, LibraryPage, and LibraryList) manage state containing lists of child components.
Do you have any recommendations on how we could improve this project for the next cohort?	It was a good project, and we wish we didn't have so much senioritis. I guess if you emphasized how cool it is that this project ties together all these amazing things we now know how to do into our first full-stack project, I would have had slightly less senioritis. (When I think about it, I have personally made every part of the project, even stuff the instructors provided for us in the API back end.)