[19.0][ADD] website_sale_product_multiple_qty

[yankinmax]

This module extends the eCommerce flow to support Sales Multiples
(packaging quantities) directly on the product page, in the cart,
and in the product configurator.

When a product (or variant) has a Sales Multiple configured,
the quantity entered by the customer on the website is automatically
rounded to a valid multiple according to the interaction type.

The rounding logic is applied dynamically when the customer:

• Opens the product page
• Changes the product variant
• Clicks the "+" (increase) button
• Clicks the "–" (decrease) button
• Manually enters a quantity
• Presses Enter inside the quantity input
• Changes quantities in the cart

[ivantodorovich]

LG, thanks @yankinmax !

Would it be possible to add a test tour with a simple test case?

[ivantodorovich]

nitpicking: I suggest math.ceil here, to always round-up instead of down; or round(rounded_qty, 0)

[yankinmax]

We want to be able to round "DOWN" also.

[ivantodorovich]

Go for round(rounded_qty, 0) then which would get the best outcome I guess.

[yankinmax]

It doesn't make any sense to add float rounding here if int is expected:
When the page is refreshed/opened we have the number rounded with zero decimal.
Adding the quantity increases to an integer.

const combinationInfo = await this.waitFor(rpc('/website_sale/get_combination_info', {
    'product_template_id': parseInt(parent.querySelector('.product_template_id')?.value),
    'product_id': this._getProductId(parent),
    'combination': combination,
    'add_qty': parseInt(parent.querySelector('input[name="add_qty"]')?.value),
    'uom_id': this._getUoMId(parent),
    'context': this.context,
    ...this._getOptionalCombinationInfoParam(parent),
}));

[ivantodorovich]

int(round(rounded_qty, 0)) then

int alone would result in, for example 1.999 -> 1.
Essentially takes only the integer part, ignoring all decimals.

with round, 1.999 -> 2