Saturday, April 8, 2023
2 changes · master
Miscellaneous changes
As a developer, when you craft your records set manually, and wrongly use the API and set something weird in `ids`, something else than a tuple of integers, `repr` should help you to understand you did something wrong. e.g. before ```py In [1]: env['res.partner']._browse(self.env, '(1,)', 'bar') Out[1]: res.partner(1,) ``` after ```py In [1]: env['res.partner']._browse(self.env, '(1,)', 'bar') Out[1]: res.partner'(1,)' ``` We could put an assert in `_browse` to make sure `
Original PR description
As a developer, when you craft your records set manually, and wrongly use the API and set something weird in `ids`, something else than a tuple of integers, `repr` should help you to understand you did something wrong. e.g. before ```py In [1]: env['res.partner']._browse(self.env, '(1,)', 'bar') Out[1]: res.partner(1,) ``` after ```py In [1]: env['res.partner']._browse(self.env, '(1,)', 'bar') Out[1]: res.partner'(1,)' ``` We could put an assert in `_browse` to make sure `ids` is a tuple of integers, but this is considered a non-stable change, as it will suddenly crashes when you will update Odoo while it wasn't the case before. Forward-Port-Of: odoo/odoo#118099 Forward-Port-Of: odoo/odoo#118076
Tag UBLVersionID should not be present for UBL Bis 3 and its inheriting formats. The fonction infering the format from an xml etree needed to be apdated too, since we can no longer rely on the `UBLVersionID` node for UBL Bis 3 and its inheriting formats. The `CustomizationID` node is used. opw-3249153 Forward-Port-Of: odoo/odoo#118092 Forward-Port-Of: odoo/odoo#118024
Original PR description
Tag UBLVersionID should not be present for UBL Bis 3 and its inheriting formats. The fonction infering the format from an xml etree needed to be apdated too, since we can no longer rely on the `UBLVersionID` node for UBL Bis 3 and its inheriting formats. The `CustomizationID` node is used. opw-3249153 Forward-Port-Of: odoo/odoo#118092 Forward-Port-Of: odoo/odoo#118024