drink-this/drink-this-backend

A cocktail recommendation app. Find your new favorite based on ratings of other users like you.

drink-this-backend's Issues

Write tests for the AuthenticationController

Request tests for the controller

db allows duplicate ratings (instead of updating the users rating if they re rate a cocktail)

make sure find and create method for ratings (in controller) isn't making new row in database when a row for that cocktail+user combination already exists

Fix Null Ids when getting a drink recommendation

End point that sends data for home page

5 rated cocktails sorted by stars

• id
• name
• stars

5 random cocktails the user has not rated

• id
• name

5 random cocktails by glass (coup in this case) that the user has not rated

• glass
• id
• name

5 random cocktails by alcohol (rum in this case) that the user has not rated

• alcohol
• id
• name

if one call is used it could look something like this

{
    "rated": {
        "cocktails": {}
    },
    "random": {
        "cocktails": {}
    },
    "glass": {
        "type": "coup",
        "cocktails": {}
    },
    "alcohol": {
        "type": "rum",
        "cocktails": {}
    }
}

Make a recommendation

As a user, when I click the button requesting a recommendation, I want to see a cocktail recommendation based on ratings I've provided and ratings from all other users in the system.

Cocktails Yelp Search

When a client sends a get request to "/api/v1/search/yelp", with a valid param in request body called "query" of type string, the response would be the results:

{
"data": [ { 
   "name": "business name",
   "address": "business address",
   "business_type": "type of business",
   "thumbnail": "business thumbnail",
   "yelp_link": "yelp link to business"
},
  { 
   "name": "business name",
   "address": "business address",
   "business_type": "type of business",
   "thumbnail": "business thumbnail",
   "yelp_link": "yelp link to business"
} ]
}

Google OAuth

As a user, I want to be able to create an account and then subsequently log into the app with Google.

Clean up SQL code for onboard endpoint

• unnecessary joins with rating table? (prioritize unrated cocktails)
• unnecessary user id
• make sure we are sending 5 unique cocktails

Cocktails Search

When a client sends a get request to "/api/v1/search/cocktail", with a valid param in request body called "query" of type string, the response would be the results:

{
"data": 
   [ {
   "id": "cocktail_id",
   "type": "cocktails_search",
   "attributes": {
      "name": "cocktail name",
      "thumbnail": "cocktail thumbnail",
      "rating": "cocktail rating"
      }
   } ,
       {
   "id": "cocktail_id",
   "type": "cocktails_search",
   "attributes": {
      "name": "cocktail name",
      "thumbnail": "cocktail thumbnail",
      "rating": "cocktail rating"
      }
  } ]
}

Cocktail details

As a user, when I click on a cocktail to visit its show page, I want to see the cocktail's recipe (ingredients and amount/measure of each), full-size image, name, glass type, and description of how to make it.

Easy Win: Search by ingredient

(FE/BE)

Remove duplicates from search (bug)

Search now can include both the cocktail from the search by name and by ingred, so I just need to ensure we're filtering any and all duplicates out.

Cocktails for Dashboard, No Ratings

As a user with no ratings stored in the DB, I want a list of cocktails that I have not yet rated. I also want to get the number of ratings I need to complete, which should drop as I rate cocktails.

Cocktail Rating

When a client sends a post "/api/v1/cocktails/:id/rating" to create a new rating, with a valid :id as an integer, the response status would be 201,

{
"data": { 
   "id": "id of rating",
   "type": "cocktail_rating",
   "attributes": {
      "user_id": "user id",
      "cocktail_id": "cocktail_id",
      "stars": "rating of the cocktail"
      }
   }
}

end point for all cocktails a user has rated

for the rated cocktails page