eagerly load work orders

Load together with orders, order items, customers and users,
which is pretty much the whole schema.

Signed-off-by: Zeljko <zeljko@zwr.fi>
front page app - first feature

Select 'random' work order

Signed-off-by: Zeljko <zeljko@zwr.fi>
unused components

These were copied from another project and committed,
but are not used nor needed.

Signed-off-by: Zeljko <zeljko@zwr.fi>
first page: order selection and box scanning

There is couple of things still missing here. Namely, box codes
are not stored anywhere (though this hardly influences the demo),
but also the Get New Order button (and similar GET request to server)
always returns the first one. There should be a mechanism to either
return random (not a bad idea for demo) or to actually see which are
done.

Signed-off-by: Zeljko <zeljko@zwr.fi>
housekeeping: remove debug log

Signed-off-by: Zeljko <zeljko@zwr.fi>
/work_order/next now returns random order

Signed-off-by: Zeljko <zeljko@zwr.fi>
fix: item->order has number and id

We actually store order that item belongs to inside
the item JSON structure, which allows less work
on the client side. But we need more fields there. We
explicitelly do not want to render the whole order to avoid
recursive rendenring of items.

Signed-off-by: Zeljko <zeljko@zwr.fi>
cosmetics: seed, order number always 6 digits

It looks better that way. Also, we reduce number of
items per order, for more effective demo.

Signed-off-by: Zeljko <zeljko@zwr.fi>
pickup use case

In this commit we implement pickup of products, substitutes,
undoing the last pick up and completing the order. It is a lot fake,
but works quite fine.

Signed-off-by: Zeljko <zeljko@zwr.fi>