Conversation
Homepage root
Trip edit form + buttons for all index/show pages
Styling added
CheezItMan
left a comment
There was a problem hiding this comment.
Rideshare Rails
Major Learning Goals/Code Review
| Criteria | yes/no, and optionally any details/lines of code to reference |
|---|---|
| Practices collaborating with git, and all team members contribute git commits and best git practices | ✔️ |
| Demonstrates understanding of relationships by giving accurate answers to the reflection questions and appropriate code in the models | ✔️ |
| Logic to calculate a driver's average rating and total earnings is located in the model, and it has unit tests | ✔️ |
| There are reasonable tests to test the validation requirements for all models | ✔️ |
| There are reasonable tests to test the relationship requirements for all models | ✔️ |
| There are reasonable tests to test the controller actions for all controllers | ✔️ |
| The app has an attractive and usable user interface | ✔️, looks really nice |
| The app uses/is compatible with database seeds | ✔️ |
Router code is clean: uses resources and RESTful routes |
✔️ |
Functional Requirements
| Functional Requirement | yes/no |
|---|---|
| On the passenger's details page, I want to be able to see total charged, list of trips, a link to edit, and delete | ✔️ |
| When adding a new passenger, I want to see errors and validations that show that a passenger must be provided a name and a phone number, so that I cannot make a passenger without name or phone number | ✔️ |
| On the passenger's details page, I can create a new trip for this passenger, with an assigned driver and no rating | ✔️ |
| On the driver's details page, I want to be able to see total earnings, average rating, list of trips, a link to edit, and delete | ✔️ |
| When adding a new driver, I want to see errors and validations that show that a driver must be provided a name and VIN, so that I cannot make a driver without name or VIN | ✔️ |
| On the trip's detail page, I want to be able to view details, assign a rating, navigate to the trip's passenger, driver, a link to edit, and delete | ✔️ |
Overall Feedback
| Overall Feedback | Criteria | yes/no |
|---|---|---|
| Green (Meets/Exceeds Standards) | 8+ in Code Review && 5+ in Functional Requirements |
Code Style Bonus Awards
Was the code particularly impressive in code style for any of these reasons (or more...?)
| Quality | Yes? |
|---|---|
| Perfect Indentation | ✅ |
| Elegant/Clever | ✅ |
| Descriptive/Readable | ✅ |
| Concise | ✅ |
| Logical/Organized | ✅ |
Summary
Really well done. This hit all the learning goals here. I did have some suggestions around returning status codes and testing. However this is a very solid submission. Nice work!
| redirect_to driver_path(@driver.id) | ||
| return | ||
| else | ||
| render :new |
There was a problem hiding this comment.
It's best to include an HTTP status code.
| render :new | |
| render :new, status: :bad_request |
| redirect_to driver_path(@driver.id) | ||
| return | ||
| else | ||
| render :edit |
There was a problem hiding this comment.
| render :edit | |
| render :edit, status: :bad_request |
| redirect_to passenger_path(@passenger.id) | ||
| return | ||
| else | ||
| render :new |
There was a problem hiding this comment.
| render :new | |
| render :new, status: :bad_request |
| redirect_to passenger_path(@passenger.id) | ||
| return | ||
| else | ||
| render :edit |
There was a problem hiding this comment.
| render :edit | |
| render :edit, status: :bad_request |
| redirect_to trip_path(@trip.id) | ||
| return | ||
| else | ||
| render :new |
There was a problem hiding this comment.
| render :new | |
| render :new, status: :bad_request |
| describe "can go online" do | ||
| # Your code here | ||
| end | ||
| describe "total earnings" do |
There was a problem hiding this comment.
Also include a test for when the driver has no trips.
|
|
||
| describe "complete trip" do | ||
| # Your code here | ||
| describe "total spent" do |
There was a problem hiding this comment.
You also need a test for when the passenger has no trips.
|
|
||
| describe "validations" do | ||
| # Your tests go here | ||
| it "had a numeric cost" do |
There was a problem hiding this comment.
You should also test that the cost is not missing.
| <div class="parallax"> | ||
| <h1 class="title"><%= link_to "🛸Ride Share Control Panel🛸", root_path %></h1> |
|
|
||
| root to: 'homepages#index' | ||
|
|
||
| resources :trips |
There was a problem hiding this comment.
Noting that the trips new/create can be nested under passenger.
Assignment Submission: Rideshare Rails
Congratulations! You're submitting your assignment. Please reflect on the assignment with these questions. These questions should be answered by all team members together, not by a single teammate.
Reflection