We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This file adds the type fields to uom.category.
Obeesdoo/product_scale_label/models/uom_category.py
Lines 7 to 21 in 0f3996a
Obeesdoo/product_scale_label/models/product_template.py
Lines 25 to 30 in 0f3996a
However, there exists already a measure_type field, with almost the same content.
https://github.com/OCA/OCB/blob/daa274eb48324d563e1096e334a5a73034be71dc/addons/uom/models/uom_uom.py#L13
Both are displayed in the view.
Should we get rid of type to replace it with measure_type ? This would need a migration script.
type
measure_type
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This file adds the type fields to uom.category.
Obeesdoo/product_scale_label/models/uom_category.py
Lines 7 to 21 in 0f3996a
It is used to compute the product_scale_unit.
Obeesdoo/product_scale_label/models/product_template.py
Lines 25 to 30 in 0f3996a
However, there exists already a measure_type field, with almost the same content.
https://github.com/OCA/OCB/blob/daa274eb48324d563e1096e334a5a73034be71dc/addons/uom/models/uom_uom.py#L13
Both are displayed in the view.
Should we get rid of
type
to replace it withmeasure_type
?This would need a migration script.
The text was updated successfully, but these errors were encountered: