kjendrzyca / corpo-food Goto Github PK

Order details chat - frontent

We should consider i18n in our application. Any suggestion guys?

Separate page for displaying order details. This is the second main screen after the dashboard.
In the future chat will be added to this view.

Currently we use browserHistory.push action every time we want to change the state and this feels like using low level api. It's ugly.
Instead we can use push action from react-router-redux or there might be even better solution.

Order details - backend

the idea is to show old orders on the dashboard lists but showing them differently to make the dashboard nice and clean

Administrating order - frontend

Hungry people in order - backend

• Remember they should be able to leave the order

There errors in the console after clean start.

Current behaviour:
The localization object is loaded as a whole, based on client's locale preferences, the fallback behaviour works only on the whole localization object level. I.E. when user has locale=es and we don't support es, the localization resources loaded in UI fall back to en (default locale)
Fallbacks do not work on a per key basis - if es localization key is present but does not contain all of the localization keys expected by the application, the application breaks with missing props React error or something similar.

Expected behaviour:
UI localization fallback work on a per key basis so that partial locale support is possible

This will need validation also, because we don't want users to accidentally save a meal without name or price

Error in console when adding an order:

Currently only the menu price is displayed as the meal price in orders.

We could add information about extra cost per meal and delivery cost per person to be calculated automatically (display the full menu price + {extraCostPerMeal} + {deliveryCost/peopleCount})

we should either:

• display the full cost with an additional option to view cost broken down in those 3 parts (menu + extra + delivery)
• display the cost broken down by default - this will probably take more space, though

Hungry people in order - frontent

• Remember they should be able to leave the order

Communication should go through redux store.
Client -> Server and Server -> Client messages should be dispatched as actions.

Should we use any kind of logger for backend? Any ideas?

if you put awer.awer in the link menu when creating orders you succesfully create orders, but that is not a valid link, so from order details you are redirected to /awer.awer

we need a consitent system of adding, validating and presenting links

Administrating order - backend