Daily updates from Odoo
Friday, October 19, 2018
2 changes
Code cleanup and technical improvements
This update renames several internal fields previously called "type" to names that better describe their business purpose, such as alarm type, server type, question type, and report type. The change makes the system easier to maintain and reduces the risk of conflicts with common programming terms, without introducing new user-facing functionality.
Original PR description
Purpose of this commit is to rename type column to something matching the the real business use of the field. That way it is easier to find and grep in the code. It also lessens potential conflicts with type build-in python function. It also lessens conflicts when using the field in JS as type is a build-in attribute. Renaming type column is a long-living issue. We choose to do it at the beginning of the v13 development to catch errors as soon as possible. This commit is linked to task ID 1896245. It is also a subpart of community PR #27599.
This update renames several generic “type” fields to names that better describe their business purpose, such as question type, line type, item type, phone call type, and alarm type. The change is mainly internal and helps teams maintain the software more reliably by reducing ambiguity and avoiding conflicts in code.
Original PR description
Purpose of this commit is to rename type column to something matching the the real business use of the field. That way it is easier to find and grep in the code. It also lessens potential conflicts with type build-in python function. It also lessens conflicts when using the field in JS as type is a build-in attribute. Renaming type column is a long-living issue. We choose to do it at the beginning of the v13 development to catch errors as soon as possible. This commit is linked to task ID 1896245. It is also a subpart of community PR #2807. It is linked to community PR odoo/odoo#27722.