Odoo/addons/pos_restaurant/static/src/js/splitbill.js, branch 14.0

[REF] pos_restaurant: migration to OWL framework

2020-05-12T12:48:58+00:00

[FIX] point_of_sale: Split bill

2020-01-28T09:00:34+00:00

Clean code and make overrides easier.

X-original-commit: 73f71ac673a4174e3bfc2b3b441b7097f939742d

[IMP] pos_restaurant: possibility to redefine new buttons and screens

2018-06-13T13:44:27+00:00

Was not able to make inheritance "action_button" and "screens" POS Restaurant
objects via "extend" or "include" functions.

Closes #25150

[IMP] point_of_sale: full pricelist support

2017-08-18T12:55:48+00:00

Before this the POS would load product.product records with
pricelist_id defined on the pos.config in context. These unit prices
were then used everywhere in the POS as-is. The POS contained no
pricelist logic at all.

This implements the full pricelist logic in the POS and provides a way
for users to choose what pricelist to apply per order. This
implementation closely follows the behavior defined in the product and
sale modules.

This includes unit tests for the get_price function and acceptance
tests. The unit tests are done in PhantomJS and ensure that get_price
returns the same as the backend returns when reading the 'price' field
on product.product.

Prices of products are displayed according to the selected
pricelist. To accomodate this the product_cache DomCache of the
ProductListWidget is now done per pricelist.

Additionally, this feature should speed up the loading of
product.product records. Now only stored product.product fields are
loaded. Before the non-stored computed 'price' field had to be loaded
for every product.product record.

[FIX] point_of_sale: is_unit has been removed

2017-05-22T23:40:12+00:00

Removed and replaced with is_pos_groupable by
fe631a36a5c7278040875434ad74039dfa1cf92a.

[IMP] point_of_sale: allow product grouping for all uom

2017-05-15T12:09:11+00:00

Purpose
=======

In POS, it is hard-codded in such a way that grouping will be done for the
uom category that has database id == 1.

Specification
=============

We have solved this issue: we have added a new boolean field in the uom category form view that

If a user chooses this option then products having that uom category will be grouped in the POS.

Both uom category Unit and Weight have been set to groupable by default.

- Removed the hardcoded part of groupable for uom which had database id == 1,
  Now grouping will be done on 'groupable' field of "product.uom", which is
  related to the field of the same name on "product.uom.category".
- Only the `Unit` uom category is grouped by default

[FIX] point_of_sale, pos_restaurant: temporary orders

2016-02-04T10:50:21+00:00

pos_restaurant creates temporary orders when splitting the bill. This
ensures those are never saved to persistent storage. As soon as the user
clicks on the pay button, the order is not considered temporary anymore
and will be saved.

Closes #10767
Fixes #10350
opw-666141

[MERGE] forward port of branch saas-6 up to bf1e999

2015-05-28T12:27:38+00:00

[MERGE] forward port of branch 8.0 up to 327e471

2015-05-21T12:50:39+00:00

[FIX] pos_restaurant: changed unit caused issue on splitting

2015-05-20T12:25:24+00:00

Commit 0fd51c2e6 changed the unit rounding from units from 1 to 0.001,
it was done mainly because it's the default unit and in the interface we
see quantities with 3 decimals after the floating point, so people might
expect to be able to set floating point quantities.

This change caused an issue when splitting a bill in the pos restaurant,
instead of a click being a piece of the product, it was 0.001 part of a
product.

This fix overrides the rounding of units in this case.

closes #6780
opw-639865