[19.0][MIG] fleet_vehicle_fuel_type_ethanol: Migration to 19.0#212
[19.0][MIG] fleet_vehicle_fuel_type_ethanol: Migration to 19.0#212DenerWilliam wants to merge 17 commits intoOCA:19.0from
Conversation
Currently translated at 100.0% (10 of 10 strings) Translation: fleet-12.0/fleet-12.0-fleet_vehicle_fuel_type_ethanol Translate-URL: https://translation.odoo-community.org/projects/fleet-12-0/fleet-12-0-fleet_vehicle_fuel_type_ethanol/pt_BR/
Currently translated at 100.0% (5 of 5 strings) Translation: fleet-15.0/fleet-15.0-fleet_vehicle_fuel_type_ethanol Translate-URL: https://translation.odoo-community.org/projects/fleet-15-0/fleet-15-0-fleet_vehicle_fuel_type_ethanol/it/
Currently translated at 100.0% (4 of 4 strings) Translation: fleet-16.0/fleet-16.0-fleet_vehicle_fuel_type_ethanol Translate-URL: https://translation.odoo-community.org/projects/fleet-16-0/fleet-16-0-fleet_vehicle_fuel_type_ethanol/es/
Currently translated at 100.0% (4 of 4 strings) Translation: fleet-16.0/fleet-16.0-fleet_vehicle_fuel_type_ethanol Translate-URL: https://translation.odoo-community.org/projects/fleet-16-0/fleet-16-0-fleet_vehicle_fuel_type_ethanol/sv/
|
Thanks for the contribution and welcome to OCA 🙂 Just a small note about the commit structure, following the official migration guide. According to the Migration to version 19.0 wiki, the expected flow is to first commit only the pre-commit auto-fixes, and then have a separate migration commit. In the current state of the PR, the changes that should belong to the migration (for example, version bump and other migration tasks) were included in the [IMP] : pre-commit auto fixes commit. Because of that, there is effectively no dedicated [MIG] : Migration to 19.0 commit. Could you please adjust the commits so that: the pre-commit commit contains only formatting / linter auto-fixes, and the actual migration changes are moved into a separate [MIG] commit, as described in the wiki? This helps keep the history clean and makes reviews and future migrations much easier. |
231f8ce to
12c64f3
Compare
|
Thank you for the welcome and for the feedback 🙂 |
|
@DenerWilliam drop this please
|
12c64f3 to
f70c4e7
Compare
|
@marcelsavegnago, done. |
| class FleetVehicleModel(models.Model): | ||
| _inherit = "fleet.vehicle.model" | ||
| default_fuel_type = fields.Selection( | ||
| selection_add=[ | ||
| ("ethanol", "Ethanol"), | ||
| ("flex", "Flex (Gasoline/Ethanol)"), | ||
| ] | ||
| ) | ||
|
|
||
|
|
There was a problem hiding this comment.
I think this code is not correct. I don’t see the need for this, since default_fuel_type is not an extensible selection field. You can remove this.
There was a problem hiding this comment.
When we remove this class, the field for selecting created models still appears normal, but when we try to create a new model, the selection field comes from default.fuel.type; in this case, these two options would not appear there.
Thanks for the explanation. I understand it now — my apologies for the confusion earlier. This approach makes sense and looks fine to me.
| "version": "19.0.1.0.0", | ||
| "license": "AGPL-3", | ||
| "category": "Human Resources/Fleet", | ||
| "author": "Escodoo,Odoo Community Association (OCA)", |
There was a problem hiding this comment.
Could you add spacing here as well? Please translate this too
"author": "Escodoo, Odoo Community Association (OCA)",
There was a problem hiding this comment.
I followed the step-by-step instructions and, as indicated, did not edit the author field, keeping it exactly as it was in the project from version 18.
Regarding the translation, I chose not to perform it since it was not a blocker for the migration. In this way, I kept the existing pattern and focused only on the adaptation needed to ensure the project runs correctly in version 19.
There was a problem hiding this comment.
I followed the step-by-step instructions and, as indicated, did not edit the author field, keeping it exactly as it was in the project from version 18. Regarding the translation, I chose not to perform it since it was not a blocker for the migration. In this way, I kept the existing pattern and focused only on the adaptation needed to ensure the project runs correctly in version 19.
It would just be the spacing, you know? Something simple
|
I don’t see any blockers, but the commit name could be: f70c4e7 |
f70c4e7 to
8db65e5
Compare
|
This PR has the |
WesleyOliveira98
left a comment
There was a problem hiding this comment.
CODE REVIEW - OK
|
@DenerWilliam Could you please check whether a PR already exists for a module before opening a new one? PR - #198 |







Up to 19.0