Skip to content
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

[14.0] mig l10n_it_rea #1930

Merged
merged 41 commits into from
Nov 26, 2020
Merged

[14.0] mig l10n_it_rea #1930

merged 41 commits into from
Nov 26, 2020

Conversation

jado95
Copy link
Contributor

@jado95 jado95 commented Oct 30, 2020

Descrizione del problema o della funzionalità:

Comportamento attuale prima di questa PR:

Comportamento desiderato dopo questa PR:

--
Confermo di aver firmato il CLA https://odoo-community.org/page/cla e di aver letto le linee guida su https://odoo-community.org/page/contributing

hurrinico and others added 30 commits October 30, 2020 14:42
[FIX] Add readme

[FIX] fix province

[FIX] Module name and description

[FIX] Fixed Register

[FIX] rem descr from __openerp__
FIX bug tracker and empty keys
[MIG] Rename manifest files
[FIX] © -> Copyright, and make module installable

[FIX] Enconding on py files
[UPD] Readme
[FIX] openerp -> odoo in xml tag

Add Authors, use https on oca web site
ADD REA fields to copany and compute company_registry accordingly
Updated by Update PO files to match POT (msgmerge) hook in Weblate.
Currently translated at 100.0% (15 of 15 strings)

Translation: l10n-italy-12.0/l10n-italy-12.0-l10n_it_rea
Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-12-0/l10n-italy-12-0-l10n_it_rea/it/
Currently translated at 100.0% (15 of 15 strings)

Translation: l10n-italy-12.0/l10n-italy-12.0-l10n_it_rea
Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-12-0/l10n-italy-12-0-l10n_it_rea/it/
Currently translated at 100.0% (15 of 15 strings)

Translation: l10n-italy-12.0/l10n-italy-12.0-l10n_it_rea
Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-12-0/l10n-italy-12-0-l10n_it_rea/it/
Updated by Update PO files to match POT (msgmerge) hook in Weblate.
Currently translated at 100.0% (15 of 15 strings)

Translation: l10n-italy-12.0/l10n-italy-12.0-l10n_it_rea
Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-12-0/l10n-italy-12-0-l10n_it_rea/it/
Currently translated at 100.0% (15 of 15 strings)

Translation: l10n-italy-12.0/l10n-italy-12.0-l10n_it_rea
Translate-URL: https://translation.odoo-community.org/projects/l10n-italy-12-0/l10n-italy-12-0-l10n_it_rea/it/
@jado95 jado95 force-pushed the 14.0-mig-l10n_it_rea branch 2 times, most recently from 02f9dd1 to 79625ce Compare November 4, 2020 11:40
@tafaRU
Copy link
Member

tafaRU commented Nov 20, 2020

@jado95 ho forzato il rebuild di runbot: vediamo se diventa 🟢

@jado95
Copy link
Contributor Author

jado95 commented Nov 20, 2020

@tafaRU Ottimo, grazie.

@tafaRU
Copy link
Member

tafaRU commented Nov 20, 2020

@jado95 in fase di revisione del codice ho colto l'occasione per apportare questo piccolo improvement: jado95#1 Consiglio di mergiarlo non usando l'opzione Create a merge commit. Grazie.

@tafaRU
Copy link
Member

tafaRU commented Nov 20, 2020

@jado95 aspetta a mergiare jado95#1 Ho visto che runbot che è ancora rosso magari sono necessarie ulteriori modifiche.

…d and fix the following warnings that are getting runbot build red. (#1)

2020-11-20 10:30:20,958 160 WARNING openerp_test odoo.fields: res.company.rea_member_type: selection attribute will be ignored as the field is related
2020-11-20 10:30:20,959 160 WARNING openerp_test odoo.fields: res.company.rea_liquidation_state: selection attribute will be ignored as the field is related
Copy link
Contributor

@robyf70 robyf70 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per il resto LGTM

[("LS", "In liquidation"), ("LN", "Not in liquidation")], "Liquidation State"
)

_sql_constraints = [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spesso questi campi non sono valorizzati, perchè non rimuoviamo il constraint?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non me ne intendo! Se ne sei sicuro, per me ok, altrimenti chiederei prima conferma a @marco-marchiori.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Si ok! Rimane comunque il problema che se una o più aziende non hanno indicato questi dati e dobbiamo creare il contatto, la creazione fallisce perchè il constraint fallisce, io l'ho rimuovo sempre nelle installazioni perchè crea solo problemi e blocca l'import delle fatture elettroniche per i fornitori nuovi

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Se i campi sono vuoti, il vincolo non viene violato:
https://www.postgresql.org/docs/current/ddl-constraints.html#DDL-CONSTRAINTS-UNIQUE-CONSTRAINTS

However, two null values are never considered equal in this comparison. That means even in the presence of a unique constraint it is possible to store duplicate rows that contain a null value in at least one of the constrained columns

Quindi non vedo problemi

Copy link
Contributor

@robyf70 robyf70 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comunque LGTM! Magari rimuoviamo il constraint dopo

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@tafaRU
Copy link
Member

tafaRU commented Nov 20, 2020

Comunque LGTM! Magari rimuoviamo il constraint dopo

Ok, allora mergio!

@tafaRU
Copy link
Member

tafaRU commented Nov 20, 2020

/ocabot merge patch

@OCA-git-bot
Copy link
Contributor

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 14.0-ocabot-merge-pr-1930-by-tafaRU-bump-patch, awaiting test results.

OCA-git-bot added a commit that referenced this pull request Nov 20, 2020
Signed-off-by tafaRU
@jado95
Copy link
Contributor Author

jado95 commented Nov 20, 2020

Ottimo!

@tafaRU
Copy link
Member

tafaRU commented Nov 26, 2020

Il merge di questa PR è rimasto bloccato per via del problema evidenziato in https://odoo-community.org/groups/contributors-15/contributors-181547
Ho eliminato il branch creato da OCA Bot e provo a rilanciare il merge.

@tafaRU
Copy link
Member

tafaRU commented Nov 26, 2020

/ocabot merge patch

@OCA-git-bot
Copy link
Contributor

On my way to merge this fine PR!
Prepared branch 14.0-ocabot-merge-pr-1930-by-tafaRU-bump-patch, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit ea3c39d into OCA:14.0 Nov 26, 2020
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at e8781e0. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.