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
It is forbidden to create move with the same source and destination locations.
To avoid this case, we remove the destination location from the quantities to
pick.
issue7856
review66541002
The value stored in a period are at the date so it should be forbidden to
create move ate this date and we can use the value up to this date.
issue7489
review45721002
If the flat location children are not explicitly in the requested locations,
they should not be included because the quantity is already included in the
parent location and they will be added twice if a single location is requested
(because of the quick loop).
issue7162
review44871003
It uses the product_uom_category field which is a Function to allow other
modules to extend the computation to enforce a specific category.
issue6839
review39791002
In case of negative quantity, the unit price is used as cost price if it is an
incoming and the cost price is kept if tit is an outgoing.
issue6770
review44311002
- Save the move state only when a second same products is going to be
proceeded.
- Write the new cost prices when the moves are saved.
- Use get_multivalue with extensible pattern using explicit company value.
- Rename _update_product_cost_price into _compute_product_cost_price
- Use grouped instances of moves with the right context to avoid to
instantiate a product on each call to _compute_product_cost_price.
issue6626
review36431002
The product quantity must be computed on all storage location but without
childs otherwise the children quantity are added a second time on parent by
Move._get_quantity
To allow this behaviour the Move._get_quantity and Move._search_quantity use
the 'with_childs' context. If the context is not set, the default value will
be False if there are more than one location. This provides a sane default
behaviour because the locations could be children from each others.
issue6627
review35491002
The search quantity can not use an having clause because the SQL query does
not sum the children. The evaluation of the domain expression must be done
after.
issue6605
review37501002
Cédric Krier