-
-
Notifications
You must be signed in to change notification settings - Fork 660
[MIG] pos_default_partner: Migration to 15.0 #759
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
Conversation
Currently translated at 100.0% (5 of 5 strings) Translation: pos-12.0/pos-12.0-pos_default_partner Translate-URL: https://translation.odoo-community.org/projects/pos-12-0/pos-12-0-pos_default_partner/es/
|
Hey @tupaq, thank you for your Pull Request. It looks like some users haven't signed our Contributor License Agreement, yet.
Appreciation of efforts, |
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.
Works as expected
|
@bealdav : could you review the migration of the module you shared ? |
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.
Lg
|
This PR has the |
|
/ocabot merge nobump |
|
On my way to merge this fine PR! |
* Print event.registration receipts. * Refunding a pos.order will cancel the event registrations. * Support pricelists. * Refactored code for better overrideability.
This allows to play nice with other modules, that may either be: * Trying to modify the created registrations * Creating registrations themselves * Or even calling `_create_event_registrations` programatically. It has no impact on functionality, though.
|
Ok @ivantodorovich. rebased and fix pre-commit |
|
This PR has the |
|
CAn you review the problem? @tupaq |
Revised and corrected. |
|
@etobella @ivantodorovich could you merge? |
|
There are some merge commits here... Can you rebase and the push force? |
|
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
No description provided.