Skip to content

Chantelle & Anibel (Chanibel) - Video Store Consumer - Edges#7

Open
anibelamerica wants to merge 72 commits into
Ada-C10:masterfrom
anibelamerica:master
Open

Chantelle & Anibel (Chanibel) - Video Store Consumer - Edges#7
anibelamerica wants to merge 72 commits into
Ada-C10:masterfrom
anibelamerica:master

Conversation

@anibelamerica

Copy link
Copy Markdown

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#5
For each person in your pair, describe something you learned from your partner during this project Chantelle is really thorough and is able to hold a lot of different concepts in her head at once. It was really helpful when remembering how to construct api calls and working with Rails. Also, CSS. She's got tricks! Anibel writes very clean and DRY code. She also uses new techniques and language features, like spread operators, currying and closure, which makes for very easy to read yet elegant code. I think her clarity balanced out my wackiness.
What was one area of React you gained more clarity on during this assignment? We gained more practice on how to integrate a React front-end with an external API.
Describe how you solved the problem of having lists of movies that look mostly the same but have different content We didn't really encounter this problem. However, when we needed to access a specific movie, we used the id assigned by the movie DB to uniquely identify it (even when other movies had similar names/release dates, etc.)
Describe how you handled rentals with React We stored the selected customer and movie in app state via callbacks from the Customer and Movie components. Whenever the user then clicks the check out button, our react app would make a post request to our Rails API that would create a new record in Rental database.
Describe a DOM event your application handled In the Search component, we had a listener for an 'Enter' keypress. This would signify that the user had submitted a complete term to query the Rails API (and would then query the external movie API).
Did you use any functional stateless components? What for? Yes, we had our StatusBar, Movie, and Customer as functional components since they were just for presenting the information.
Did you use any container components? What for? Yes, for the App, Library, Search, and Customers components since they stored state and functions for behavior.
Do you have any recommendations on how we could improve this project for the next cohort? It would have been cool to deploy with AWS and try out Yarn

In case you needed links:
http://chanibel-video-store-consumer.surge.sh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants