Kiera & Luxi - Rideshare - Octos

[Lindseyls]

Rideshare-Rails

Congratulations! You're submitting your assignment! These comprehension questions should be answered by both partners together, not by a single teammate.

Comprehension Questions

Question	Answer
Describe the types of entity relationships you set up in your project and why you set up the relationships that way	We had three entity relationships. We wanted to make every trip have one passenger and one driver. Then, each passenger and driver would have many trips. Therefore, the trips is essentially acting as the intermediate table.
Describe the role of model validations in your application	The role of model validations is to ensure that the user while creating or editing a passenger, trip or driver, they must fill in the correct information or provide all the necessary information.
How did your team break up the work to be done?	We worked on the components that we felt were very important to tackle together including setting up CRUD and Restful routes, and also trips. We separated the passenger and driver so that we could work on the two sections on our own separate branches then merged back together into master.
What features did you choose to prioritize in your project, and what features, if any, did you have to set aside to meet the deadline?	We prioritized to tackle each section as much as we can. We wanted to have all the basic concepts and logics down. The one thing that we were unsure that we can get to was the CSS part, which unfortunately we were not able to do very much. Also, our validations could be more thorough.
What was one thing that your team collectively gained more clarity on after completing this assignment?	We got more clarity on nested routes, how to incorporate CSV through seeding, and how all the different components relate to each other.
What is your Trello URL?	https://trello.com/b/LiCpbKgj/rideshare-rails
What is the Heroku URL of your deployed application?	https://k-and-l-rideshare.herokuapp.com/
What are two discussion points that you and your pair discussed when giving/receiving feedback from each other that you would be willing to share?	We did not get a chance to discuss this extensively. But, we both felt that we worked really well together resolving issues and checking off tasks as we go. Trello was a great tool to use to keep us on track.

[droberts-sea]

Rideshare-Rails

What We're Looking For

Feature	Feedback
Baseline
Appropriate Git Usage with no extraneous files checked in and both partners contributing	yes
Answered comprehension questions	yes
Uses named routes (like _path)	yes
RESTful routes utilized	yes - some extra, see inline
Rideshare Rails Specific Content
Table relationships	yes
Validation rules for Models	yes
Business logic is in the models	yes - good work
Database is seeded from the CSV files	yes
Trello board is created and utilized in project management	yes
Postgres database is used	yes
Heroku instance is online	yes
The app is styled to create an attractive user interface	some - this could definitely use some work
Overall	Good work overall! There are a few places where things could be cleaned up, which I've tried to call out below. However, the core flow of the application works fine, and it seems to me that the learning goals were met. Keep up the hard work!