This mini project is created for demo RoR. Click me to have a try

Menu of a coffee shop:

Please code a simple app for this coffeeshop. The coffee shop requirements:

1. Adding orders
2. Keep track of all orders (total sales)
3. Group orders by type of orders (coffee or tea)
4. Group orders by type of size (tall, grande or venti)

Additional questions:

1. What if we want a new type of coffee, a new type of tea?
2. What if we want a new size?
3. How would you change the model to add hot/cold options?
4. (optional) How would you change the model to support adding condiments to drinks (perl, grass jelly,...)

You're free to use whatever database you feel like.

• You are free to choose any server side technologies for the API. Using nodejs is a plus.
• Using polymer or reactJS as a library for the view components. Feel free to apply any other JS frameworks. Polymer is a big plus as we are using Polymer now.
• Tests are recommended and bonus points if you can deploy it to Heroku. When you're done, please post your code to GitHub or Bitbucket along with a detailed Readme.
• Good UI/UX is a another plus.

1. Click dropdown Make a order to make a new order. Order listing below will auto update once order create successfully.
2. Click dropdown Group by Type to filter all orders with that drink type.
3. Click dropdown Group by Cup to filter all orders with that Cup size.
4. Group Group by Type and Group by Cup is combinational support.
5. Order listing will show most 5 orders per page.

• If the result count is larger than 5, pagination will show.
• If no result found, text 'No result found' will show.

6. Click Refresh icon to refresh the order listing.

• Here assume server response time is 2 second. 'Debounce' was use here to protect server overload in case of keep pressing 'Refresh'.

7. Total sales will auto update once the orders listing was updated.

Font Awesome + ReactJs + React on Rails + React Bootstrap + jQuery + Rails+ Postgresql + Heroku (Host)

gem rspec-rails was used to test rails model && controller.

Three tables was designed for the mini app:

1. drinks

• [name:varchar]: Name of the drink like 'Espresso' 'Hot Tea'
• [drink_type:varchar]: drink type: 'coffee' or 'tea'

2. items

• [drink_id:integer]: foreign key of table drinks, refer the drink.
• [price:integer]: price of that drink. Use integer here, if need show on front-end, divide by 100.
• [cup_size:varchar]: Cup size of the drink, i.e. 'tall' 'grande' 'venti'

3. orders

• [item_id]: foreign key of table items, refer the item ordered.

1. What if we want a new type of coffee, a new type of tea?

If have a new type of coffee or tea like 'Red Tea', firstly create new drink with [name='Red Tea', drink_type='teas'], then create new items base on the cup size like [drink_id: 'id of red tea drink', cup_size: 'tall|grande|venti', price: 6.66]

2. What if we want a new size?

Current design assume that the cup size not change so frequently. There are two ways for that feature change. One way is create new record in table items, for example, 'Espresso' with cup size 'mini': [drink_id:'espresso drink id', cup_size: 'mini', 'price': 1.22]. Code and test case need change for this feature. The other ways is refactor the database: create a new table to store cup_size which similar as table drinks. We may call it table cups: [name:varchar]. If have a new size like 'mini', create a new record in that table.

3. How would you change the model to add hot/cold options?

Depends on the product logic. If price is same for hot and cold, add a new column to table orders, otherwise add a new column to table items.

4. (optional) How would you change the model to support adding condiments to drinks (perl, grass jelly,...)

Suppose that each drink item can add many condiments and the price is different for different combinations. We may create new table called condiments with two columns [name:varchar, price:integer], and add two new columns to table orders [c_price:integer, c_list:varchar]. When create new order, sum all the choose condiments price then store it in orders:c_price, and concat the name of condiments then store it in orders:c_list.

• In the case images not shown properly, please refer the asset folder.