-
-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
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
[MIG][12.0] partner_delivery_schedule: Migration to v12.0 #236
[MIG][12.0] partner_delivery_schedule: Migration to v12.0 #236
Conversation
…hedule to partners (OCA#164)
… incoming pickings too. Translated using Weblate (Spanish) Currently translated at 100.0% (26 of 26 strings) Translation: delivery-carrier-11.0/delivery-carrier-11.0-partner_delivery_schedule Translate-URL: https://translation.odoo-community.org/projects/delivery-carrier-11-0/delivery-carrier-11-0-partner_delivery_schedule/es/
f2eef14
to
1359315
Compare
1359315
to
d248906
Compare
@pedrobaeza Changes done!! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code review
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe you can implement this later by having in re.partner a Many2one with resource.calendar instead of a Many2many with delivery.schedule and so we will have one less model to worry about and maybe the allow_delivery_date method could be shorter.
If it is not done in the migration of this module it could be done as an improvement later. What do you think ?
/ocabot merge |
On my way to merge this fine PR! |
Congratulations, your PR was merged at 2e960f4. Thanks a lot for contributing to OCA. ❤️ |
cc @Tecnativa TT20121
@ernestotejeda @rafaelbn review please!!