-
-
Notifications
You must be signed in to change notification settings - Fork 179
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] l10n_eu_nace #176
Conversation
Short category names are now displayed on partner views, since NACE names are so long
Data files were there, but translations were not.
[ADD] setup.py
[12.0][IMP] - Add unit tests [IMP] - code improve Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/migrations/12.0.2.0.0/pre-migration.py Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/migrations/12.0.2.0.0/post-migration.py Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/models/res_partner_nace.py Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/models/res_partner_nace.py Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/models/res_partner_nace.py Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/models/res_partner_nace.py Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/models/res_partner.py Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/models/res_partner_nace.py Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/views/res_partner.xml Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/readme/CONTRIBUTORS.rst Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/models/res_partner_nace.py Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/models/res_partner_nace.py Co-authored-by: Jairo Llopis <[email protected]> [FIX] - fix code Update l10n_eu_nace/models/res_partner_nace.py Co-authored-by: Jairo Llopis <[email protected]> [FIX] - Fix name_search
Fix post-migration Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/models/res_partner_nace.py Co-authored-by: Jairo Llopis <[email protected]> Update l10n_eu_nace/models/res_partner_nace.py Co-authored-by: Jairo Llopis <[email protected]>
Some need to add secondary NACE codes to partners. This is a very little addition, possibly quite standard, so it's done directly in the base addon. @Tecnativa TT17678
FIX + IMP : more readable query for updating partners with new xml_id regarding old xml_id
Currently translated at 100.0% (868 of 868 strings) Translation: community-data-files-14.0/community-data-files-14.0-l10n_eu_nace Translate-URL: https://translation.odoo-community.org/projects/community-data-files-14-0/community-data-files-14-0-l10n_eu_nace/fr/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: community-data-files-14.0/community-data-files-14.0-l10n_eu_nace Translate-URL: https://translation.odoo-community.org/projects/community-data-files-14-0/community-data-files-14-0-l10n_eu_nace/
hum... runboat not available! issued a 404 |
It works for me, can you try it one more time? |
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.
functionnal test OK,
LGTM
Hi, Thanks for the PR request. Is it possible to fix it before please ? |
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.
After analyzing this module, I think it needs a refactor. Please let me explain.
This module introduces a duplicate structure in Odoo. Odoo CE already has a res.partner.industry
model. In OCA, the partner_industry_secondary
module implements:
- Parent-child relationship.
- Many2many relation between
res.partner
andres.partner.industry
.
So, if this module depends on partner_industry_secondary
, which is already migrated to v16, we can drop most of the code. This would just contain the NACE codes in CSV, which would be declared in the manifest and loaded at install; period.
IMHO the migration is probably the best opportunity to do it, as this involves structural changes in the data model. It would mean directly dropping all xml and python code from here, so I think it's a simple refactor that'd be very helpful.
FWIW the only "complex" thing would be a migration script, which wouldn't be very complex anyways.
WDYT?
Looking at the modules I totally agree with you. |
The only problem I see is that the industry model already contains other records that are not NACE ones. |
Which ones? By quickly looking (at least for v16) it seems right to me... |
Yes, but these are the main existing NACE groups. See https://en.wikipedia.org/wiki/Statistical_Classification_of_Economic_Activities_in_the_European_Community or https://nacev2.com/en |
Ok then. Just a proper mapping should be done for recognizing them as the parents. |
|
Hello @Abranes, are you going to change your PR according to comments above ? |
/ocabot migration l10n_eu_nace |
Sorry @rafaelbn you are not allowed to mark the addon tobe migrated. To do so you must either have push permissions on the repository, or be a declared maintainer of all modified addons. If you wish to adopt an addon and become it's maintainer, open a pull request to add your GitHub login to the |
Thanks! Closing here, as the other PR is more suited for merge. |
Migrated in #196 |
Standard migration to 16.0