-
-
Notifications
You must be signed in to change notification settings - Fork 603
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
[16.0] [MIG] pos_event_sale: Migration to 16.0 #1205
base: 16.0
Are you sure you want to change the base?
Conversation
@ivantodorovich , continue the pr of @BT-dmoreno (#1022) Here. |
e9d3004
to
28ec285
Compare
Thanks @maq-adhoc ! CI is still broken, though. |
@ivantodorovich , this week I want to leave all the tests ok. When it's ready I'll let you know |
/ocabot migration pos_event_sale |
The migration issue (#849) has not been updated to reference the current pull request because a previous pull request (#1022) is not closed. |
2325ccf
to
de173b9
Compare
c1b3a42
to
880624e
Compare
7e8997b
to
d6a1b82
Compare
87fed76
to
843c094
Compare
By default, the longPressDelay is 1000ms which is not intuitive and makes it pretty much unusable in touchscreen devices. In this case, it makes no sense to have a delay for selecting dates. By setting it to 0 we're effectively disabling the pressDelay, and the user experience is much better.
* Print event.registration receipts. * Refunding a pos.order will cancel the event registrations. * Support pricelists. * Refactored code for better overrideability.
… pos_order_line before installation This helps to avoid a Memory Error when installing this module on an instance with a big amount of existing pos_order_line
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: pos-15.0/pos-15.0-pos_event_sale Translate-URL: https://translation.odoo-community.org/projects/pos-15-0/pos-15-0-pos_event_sale/
When paying a `pos.order`, confirm only the `event.registration` that are in draft state. Don't attempt to confirm the ones that are already confirmed, nor the ones that might be cancelled.
If we cancel a `pos.order`, we should cancel the related `event.registration`(s) However, if the `event.registration` is already done, we should not cancel it as it would be already too late to do so.
Registrations created from the PoS are not to be confirmed automatically. We confirm them when the `pos.order` is paid, but they are to remain in `draft` until then.
In the PoS, if the order is not paid, then it's not confirmed. If it's not confirmed, then we might as well ignore it. We shouldn't cancel any existing registrations until then.
Negated lines are particularly useful with PoS modules that disable the removal of pos orderlines through the use of ``disallowLineQuantityChange``. This is the case of `l10n_fr_pos_cert` module, for example. But there are other core modules doing it, too. In this case, added order lines can't be removed. Instead, the cashier is encouraged to add a negative to 'cancel' the original one. e.g.: Adds a line with 10 tickets. Then, adds a line with -10 tickets. This should be almost the same as removing the first line: no actual registration should be confirmed in the end, as we're reverting this sale.
Moved some ORM tests to `tests_backend`, that will execute faster than tours. Added unit tests to cover more backend scenarios.
EventEventTicket inherits from EventTypeTicket, so we don't need to duplicate the field declaration, if it is the same in both module. This ease overriding, as we need to override only one model, if we expect the same behavior in both.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: pos-15.0/pos-15.0-pos_event_sale Translate-URL: https://translation.odoo-community.org/projects/pos-15-0/pos-15-0-pos_event_sale/
Currently translated at 100.0% (73 of 73 strings) Translation: pos-15.0/pos-15.0-pos_event_sale Translate-URL: https://translation.odoo-community.org/projects/pos-15-0/pos-15-0-pos_event_sale/it/
843c094
to
0359f1e
Compare
No description provided.