buildo / pronto Goto Github PK

requirements

minimal layout with

• navbar links
  • view orders
  • edit menu
  • edit profile
• open toggle button

specs

{optional: describe technical specs to implement this feature, if not obvious}

misc

{optional: other useful info}

← #7

requirements

• create the component to display the restaurant's menu
  • menu can be readOnly or canInteract

specs

{optional: describe technical specs to implement this feature, if not obvious}

misc

{optional: other useful info}

← #3

requirements

• define the route to retrieve the restaurants list

specs

{optional: describe technical specs to implement this feature, if not obvious}

misc

{optional: other useful info}

requirements

{describe the new feature}

specs

{optional: describe technical specs to implement this feature, if not obvious}

misc

{optional: other useful info}

← #12

requirements

• below #15
• display other infos (address, tel, timeSlot )
• props
  • address (String)
  • tel number (String)
  • timeSlot: TimeStart - TimeEnd

specs

• FlexView
• ask @francescogior and @alessandravilla for mockup

misc

{optional: other useful info}

← #12

requirements

first part of RestaurantDetailsHeader component: display big beautiful restaurant image (💇 ) + name + description

• props:
  • imageURL (String)
  • name (String)
  • `description (String)

specs

• use FlexView for the layout
• talk to @alessandravilla and @francescogior for mockup

misc

{optional: other useful info}

← #3

requirements

display some restaurant details information as a "card"

props:

• imageURL (String)
• name (String)
• timeSlot (I don't how this is defined) [~String,~String] (?)
• address (String)
• onClick (Function)

specs (mockup)

talk to @alessandravilla and @francescogior

← #5

requirements

• there should be a component named Cart

specs

misc

{optional: other useful info}

← #7

requirements

• as for title

specs

{optional: describe technical specs to implement this feature, if not obvious}

misc

{optional: other useful info}

requirements

• orders should be sorted by date desc
• should allow to show detail for each order

specs

{optional: describe technical specs to implement this feature, if not obvious}

misc

{optional: other useful info}

← #5

requirements

this component will be used as header in the restaurant page (/:restaurantId)

display every restaurant detail

sub-issues

• HeaderImage + background image #15
• details grid #16

requirements

{describe the new feature}

specs

{optional: describe technical specs to implement this feature, if not obvious}

misc

{optional: other useful info}

requirements

make CreateOrder page

specs

somehow

misc

{optional: other useful info}

requirements

• redefine route structure

requirements

A customer must be able to browse a list of the available restaurants, checking the information about them.

specs

TBD

sub-issues

• RestaurantCard #9
• Restaurants route structure #18

requirements

user should be able to edit restaurant properties:

• refer to Restaurant.maxPeople.. and all of RestaurantProfile for now (api is slightly changed, but fields are the same)
• plus: imageURL

specs

{optional: describe technical specs to implement this feature, if not obvious}

misc

{optional: other useful info}

requirements

setup routes and main components for restaurant/Orders

specs

{optional: describe technical specs to implement this feature, if not obvious}

misc

{optional: other useful info}

requirements

macro layout

specs

• routes
• use layout components from #46

misc

{optional: other useful info}

requirements

{describe the new feature}

specs

{optional: describe technical specs to implement this feature, if not obvious}

misc

{optional: other useful info}

requirements

A customer wants to see the restaurant details.

specs

TBD

sub-issues

• Static Menu #7
• Restaurant Details Header #12
• Order Right Sidebar #26
• Cart component #29

requirements

it should be used in Order and PersonOrder

specs

• use two different containers
• follow mockup on zeplin
• optionally deletable (only in Order)
• optionally editable (only in Order) (why not simply "clickable"??)

misc

{optional: other useful info}

← #8

requirements

A customer must be able to submit the order.

Any customer can perform this action.

Upon submit, the customer is asked a phone number.

specs

TBD

← #5

requirements

• in the routes
  • /:restaurandId
    • has only a Button with label Create order
    • more details #26 (comment)
  • /:restaurandId/:orderId => display the list of people, can add/edit/remove people, can submit order from here
  • /:restaurandId/:orderId/:personId => display items of person, can add/remove items, can confirm or cancel changes

specs

props

• Order
  • id: maybe(String), // :orderId`; if absent, the cart is empty
  • status: submitted | pending
  • referencePhoneNumber: maybe(t.String)
  • people: list(Person)
• Person:
  • name: String
  • items: list(String)

misc

route /:restaurantId

• orderId is undefined, display only a button
• on button click it should
  • call to API to create an Order resource, get back an orderId and transition to /:restaurandId/:orderId

← #10

requirements

A customer must provide a unique name when adding an order item.

If the name is already take, it should display an error message and prevent moving forward.

specs

Maybe a modal

requirements

we are going to poll data from firebase

specs

render something like:

<Poll interval={1000} callback={() => { console.log('interval'); }} />

(passing a refresh command)

in every route we need data refreshing

misc

{optional: other useful info}

← #10

requirements

• Users should be able to compose their menu
• A menu may have additional free info written by the restaurant
• should be stateless
  • value ---> big JSON
  • onChange
• for now forget about à-la-carte groups

specs

• strictly follow Menu schema described in /model/index.js

misc

{optional: other useful info}

description

as for title

how to reproduce

• {optional: describe steps to reproduce defect}

specs

{optional: describe a possible fix for this defect, if not obvious}

misc

{optional: other useful info}

requirements

{describe the new feature}

specs

{optional: describe technical specs to implement this feature, if not obvious}

misc

{optional: other useful info}

requirements

make it work

specs

somehow

misc

{optional: other useful info}

← #8

requirements

A customer must be able to add their own order

specs

TBD

sub-issues

• ask for name #17
• implement composable menu #4

← #8

requirements

A customer must be able to view the order items list, e.g. the order items already inserted by other people, if any.

route /:restaurantId/:orderId

it should

• be able to transition to /:restaurantId/:orderId/:personId
• display the list of Persons
  • and items of each person
• when click on person name it should transition to /:restaurantId/:orderId/:personId (to edit person's order)
• hovering on person name, it should show a X button to remove the person, after a confirmation modal (confirm to delete)
• there should be a button add Person
  • on click it should prompt a modal to add person's name (:personId)
  • on confirm, it should transition to /:restaurantId/:orderId/:personId
  • if the list is empty, it should behave like if one has clicked add Person (prompt modal)

specs

TBD

requirements

• define components to organize layout

specs

{optional: describe technical specs to implement this feature, if not obvious}

misc

{optional: other useful info}

description

• there should be
  • timeSlot
  • category
  • address

← #5

requirements

Display a static version of the menu, so that users can see what the restaurant offers

specs

TBD

sub-issues

• Create Menu component #21
• Use Menu in restaurant details page #22

• /:restaurandId
  • /:orderId
    • /:personId

and routehandlers

requirements

Display restaurant info in restaurant page

specs

Probably reuse the same component as the list

requirements

Printer should filter orders using index on status, checking for equalTo=submitted

specs

curl https://pronto-9842a.firebaseio.com/orders/1.json\?orderBy\=\"status\"\&equalTo\=\"submitted\"

requirements

• Elencare tutti i ristoranti (solo informazioni per gli utenti, niente ordini)
  GET /restaurants.json
• Elencare le informazioni per un ristorante
  GET /restaurants/{rid}.json
• Aggiungere un ristorante
  PUT /restaurants/{rid}.json { open: boolean, maxPeopleNumber: uint, name: String, description: String, telephone: String, address: String }
• Mostrare il menù per un ristorante
  GET /restaurants/{rid}/menu.json
• Creare un menù per un ristorante
  PUT /restaurants/{rid}/menu.json { description: String, groups: [{name: String, items: []}] }
• Elencare gli ordini di un ristorante
  GET /orders/{rid}.json?orderBy=:key&startAt=:from&endAt=:to
• Creare un ordine per un ristorante
  PUT /orders/{rid}/{oid}.json { status: "pending" }
• Mostrare un ordine per un ristorante
  GET /orders/{rid}/{oid}.json
• Aggiungere una persona all’ordine
  PUT /orders/{rid}/{oid}/peopleOrders/{uid}.json { orderItems: [String] }
• Submit un ordine
  PATCH /orders/{rid}/{oid}.json { customerPhoneNumber: String, status: "submitted" }

requirements

A customer must be able to place an order

specs

TBD

sub-issues

• Add my order #10
• Submit order #11
• Order Item list #13

requirements

see title

specs

queries

misc

{optional: other useful info}