jsjohn026/playbnb

playbnb's Issues

MVP List

You should try to stick to the MVP List that aA provides for AirBnB. Listings and Bookings are fine, but Reviews should be a separate MVP from Bookings and Listings.

Listings

• Users should be able to create a new listing and upload pictures for that listing
• Reviews should be a separate MVP from Listings

Bookings

• For AirBnB, a user can request to book a listing. The owner of the listing can then approve or disapprove the listing.
• Reviews should be a separate MVP from Bookings

Dashboard and Profile

• should be a bonus MVP

Sample State

users

• a user should have a key of listingIds that is an array that points to all the listings created by that user
• a user should have a key of bookingIds that is an array that points to all the bookings created by that user

listings

• a listing should have a key of reviewIds that is an array that points to all the review ids for that listing
• a listing should have a key of avgRating, which will be a number that is displayed for the average rating of a listing based on reviews (even though this doesn't exist on the listings table as a column)

errors

• bookingsForm should not appear twice as a key

Nice Sample State!

Frontend Routes

logging in and signing up

• looks like logging in and signing up on AirBnB is done using modals and they don't have specific routes like /login or /signup for those forms

Nice job on your frontend routes!

Schema

listings

Nice listings table! When you start off your project, all those columns can be really daunting, so I would suggest starting off with just a few columns. Getting the feature to work with those few columns is much easier than trying to get your feature to work properly first with all those columns. You can add the columns in after.

• should not have a unique index on user_id because a user can create many listings

bookings

• guest_id should not be unique because a guest can have multiple bookings

hosts

• do not need this table because a host is a user

Backend Routes

reviews

• routes for editing and deleting a review do not have to be nested under listings because we just use the review_id to find the review to edit or delete

great job on your backend routes!