[17.0][MIG] pos_partner_birthdate #1104
Conversation
Module for adding the birthdate in the customer screen of the POS.
Currently translated at 100.0% (2 of 2 strings) Translation: pos-16.0/pos-16.0-pos_partner_birthdate Translate-URL: https://translation.odoo-community.org/projects/pos-16-0/pos-16-0-pos_partner_birthdate/it/
…en birthdate field is empty.
Currently translated at 100.0% (2 of 2 strings) Translation: pos-16.0/pos-16.0-pos_partner_birthdate Translate-URL: https://translation.odoo-community.org/projects/pos-16-0/pos-16-0-pos_partner_birthdate/es/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: pos-16.0/pos-16.0-pos_partner_birthdate Translate-URL: https://translation.odoo-community.org/projects/pos-16-0/pos-16-0-pos_partner_birthdate/
…date_date use useState
…e=birthdate_date/>
|
/ocabot migration pos_partner_birthdate |
Co-authored-by: rousemilano <routhberism@gmail.com>
etobella
force-pushed
the
17.0-mig-pos_partner_birthdate
branch
from
8fd605b to
da6b956
Compare
|
@etobella do you know why the birthdate field in the pos is not sensitive to language ? I tested it with a user having english language and the date format is jj/mm/aaaa |
|
@cvinh I followed the same logic we find in other date fields inside PoS. https://github.com/odoo/odoo/blob/17.0/addons/point_of_sale/views/pos_ticket_view.xml#L160-L162 When I was checking it, I had similar issues, but at the end I choose to follow the same logic applied to other date fields. |
|
This PR has the |
|
/ocabot merge nobump |
|
/ocabot merge nobump |
|
What a great day to merge this nice PR. Let's do it! |
|
Congratulations, your PR was merged at b9e1429. Thanks a lot for contributing to OCA. ❤️ |
Migration to 17.0
@cvinh