gregimba/mixr

Tinder for drinks

mixr's Issues

Axios request

Uber for Coasters

Without the companion uber for coasters, people using Mixr will likely cause rings on wooden tables. Both apps should be co-developed.

Ingredient Images

• Add image column in Ingredients model
• Add ingredient images in Ingredients table in the database
• Add image to the query in the /user/:userId/ingredients query so that images can be displayed for swiping

Load drink images with API request

Import data from api

Create File Structure

• Setup client

• setup server

Match set of ingredients with drinks they can make

When a user likes an ingredient, the app should check to see if any new drinks can be made given the new state of the list of the users liked ingredients.

Server to DB queries

working on the queries made to the database

Update routes

Update routes to match the database models updates

CSS / Styling

Combine the users and the Users tables

Provide Drink Images

Update res obj in routes

Update the res obj to the client to better match the DB table info. Make them less specific.

Bad syntax in the constructor in the state object

Mixr/client/src/index.jsx

Line 17 in 3f8b16a

currentIndredient = {},

Lines 17, 18, and 19 on client/src/index.jsx have an = sign rather than : in the state object.

Sidebar / Drink List

Add Drink Matches List to POST res

Add the matchUserWithDrinks function as the res to the client after likes have been posted in the server to the user_ingredients table in the DB.

Implement matchUserWithDrinks into POST /ingredient route

Implement google-images module to fetch ingredient images in routes

Make matchUserWithDrinks a promise

Clicked Drink Component

Remove image search function from randomImage route

Database

• refactor imports as objects not functions

• Implement measures on ingredients and drinks table

• fix unique spelling

• Use dotenv

• Submit pull request and review with a team member Do not merge