dannam83 / eatery Goto Github PK

• DB: reviews
• model: review
• controller: reviews
• views: reviews, review

assign to advisor when ready

• css ftw

assign to advisor when ready

• reviewsContainer
• reviews
• should show with business Id
• should show with user Id

• README page

• style the search bar
• search should render the next page correctly upon submission
• search should autofill as typing

Hey the proposal looks pretty good! Here are some notes:

1. We're going to use paperclip to handle uploading our images and it has an interface to create the proper columns for our models. So we can talk about how to use that in a few days when images come in to play.

2. You have an array of image_urls for your businesses. If you want to business to have multiple images, there should probably be a table to hold these images and a foreign key to reference the businesses.

3. Storing lat and lng in your database for your businesses will make integrating with the map a lot simpler in the long run so I think you should ditch the address column.

-search should be able to query and pull up the appropriate businesses

learn how to implement a map
-shows in the right place
-shows current location
-shows restaurant location
-calculates distance and time to restaurant

• businesses adequate
• appropriate seeding

assign to advisor when ready

DB: businesses
model: business
controller: businesses
views: businesses

• component for search results
• component for individual business

assign to advisor when ready

assign to advisor when ready

assign to advisor when ready

CSS it to death

DB: users
model: user
controller: users/session
views: users/session

Hey the proposal looks pretty good! Here are some notes:

1. We're going to use paperclip to handle uploading our images and it has an interface to create the proper columns for our models. So we can talk about how to use that in a few days when images come in to play.

2. You have an array of image_urls for your businesses. If you want to business to have multiple images, there should probably be a table to hold these images and a foreign key to reference the businesses.

3. Storing lat and lng in your database for your businesses will make integrating with the map a lot simpler in the long run so I think you should ditch the address column.

4. Your sample state looks really solid. The only thing I would say you should be sure of is that your current user's information is in your state somewhere. You can either put it in the session slice of state or in the general users slice of state but it's gotta be somewhere.

5. You have a backend endpoint that returns a user's reviews. This is a good thought but you might not end up needing this. I'm assuming if you have a user profile page you would just fetch the reviews at the same time you fetch the rest of the user's information.

6. ^ Same deal with business reviews.

7. You probably don't need a route to get an individual review because they will be on the business show page.

Overall looks solid though, I'm excited to see how this turns out!

ajax: fetchBusinesses, fetchBusiness
actions: receiveBusinesses, receiveBusiness
reducer: RECEIVE_BUSINESS, RECEIVE_BUSINESSES

• smooth navigation
• user profile has a reviews button that shows all reviews
• business profile shows all reviews
• business has a button to submit a review

assign to advisor when ready

• search should properly show results
• business profile page has all correct information
• user should be able to sign in, and then search for a business

• ajax: fetchReviews(bizId), fetchReviews(authorId)
• actions: receiveReviews, receiveReview
• reducer: RECEIVE_REVIEWS, RECEIVE_REVIEW