The internal quantity is stored without precision constraint and so the sum
result of many rows cumulate the rounding issue.
So the quantity must be rounded to return correct result when operator is
equality.
But as getting the digits from the product default uom would require to make
many joins, the simplest and more efficient solution is to use the highest
digits of the units.
issue11235
review390001002
We can save the cost values only when a cost value was computed for a product
already moved.
Also FIFO requires to save extra moves which can be included in the save loop
so the Move._do method returns an extra list of moves to save.
issue10640
review369361002
When modify in __setup__ the domain of a field defined in the same class, this
alter the original copy of the field. So the domain is appended to itself on
each __setup__ call (each time the model is extended by another module).
issue10406
review336241002
Staging moves are automatically assigned when purchased so
we should remove them when packing a shipment as they are
not part of the shipment.
We also skip moves with zero quantity because they will
always succeed.
issue9448
review313951002
As the inventory creates and do the moves in the same transaction, the warning
about effective date in future can not be ignored (the ids change).
Also the warning name should be based on an ordered list of record to ensure to
generate always the same name.
issue9707
review328441002
We can use the compute quantities query if the request is for a single location
because all the locations are children and so we can do a SUM.
issue9594
review323991002
We add a common method to round prices that are stored using the price digits.
It is useless to use the digits from the field because it can not be changed in
any other way than by configuration.
issue9146
review299521002
We add the flake8 configuration used so we ensure everyone uses the same.
We remove the usage of __all__ for non public API.
When possible, we rationalize the class name according to its __name__ and module.
issue9082
review297061002
An empty stock_date_end is converted into max date in compute_quantities_query
and forecast context should be explicitly disable.
issue9044
review282931002
The windows that display product quantities should explicitly manage the
stock_skip_warehouse context to ensure static result.
issue9041
review253051002