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][FIX] l10n_it_fiscal_document_type get only possible fiscal document type #4340

Open
wants to merge 1 commit into
base: 14.0
Choose a base branch
from

Conversation

sergiocorato
Copy link
Contributor

@sergiocorato sergiocorato commented Aug 28, 2024

Ho inoltre corretto un test in cui l'intenzione credo fosse di creare delle fatture e non dei movimenti contabili.

Copy link

@MaurizioPellegrinet MaurizioPellegrinet left a comment

Choose a reason for hiding this comment

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

Test funzionale: OK

Copy link
Contributor

@SirAionTech SirAionTech left a comment

Choose a reason for hiding this comment

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

Grazie della PR!
Ho verificato che il problema esiste in 14.0 ed è risolto da queste modifiche.

Potresti aggiungere una nota nell'help del campo account.fiscal.position.fiscal_document_type_id per indicare come mai quella posizione fiscale non verrà sempre applicata come succedeva prima?

l10n_it_fiscal_document_type/tests/test_doc_type.py Outdated Show resolved Hide resolved
@sergiocorato sergiocorato force-pushed the 14.0-fix-l10n_it_fiscal_document_type-get-only-applicable-document-type branch 3 times, most recently from de24389 to 20a883c Compare September 3, 2024 16:55
Copy link
Contributor

@SirAionTech SirAionTech left a comment

Choose a reason for hiding this comment

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

Grazie ora si capisce un po' meglio cosa succede; ho indicato un paio di casi che mi sembrano duplicati, puoi verificare?

Comment on lines 53 to 54
# Create a customer invoice for a partner with a fiscal position with TD10,
# which is not applicable for "out_invoice" so it's applied the default TD01
Copy link
Contributor

Choose a reason for hiding this comment

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

Questo caso è testato anche sotto nell'altro test: se ne può rimuovere uno? Altrimenti puoi evidenziare che differenza c'è?

Comment on lines 63 to 64
# Create a vendor invoice for a partner with a fiscal position with TD10,
# which is applied as applicable for "in_invoice".
Copy link
Contributor

Choose a reason for hiding this comment

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

Questo caso è testato anche sotto nell'altro test: se ne può rimuovere uno? Altrimenti puoi evidenziare che differenza c'è?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah vero, lo avevo messo sotto poi, grazie.

@sergiocorato sergiocorato force-pushed the 14.0-fix-l10n_it_fiscal_document_type-get-only-applicable-document-type branch from 20a883c to 71c3b1f Compare September 5, 2024 09:46
Copy link
Contributor

@SirAionTech SirAionTech left a comment

Choose a reason for hiding this comment

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

L'ho notato solo ora con l'ultimo push, non so se era così anche prima, ma potresti modificare il messaggio del commit in modo che segua le linee guida https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst#71commit-message?
In particolare

please check if the commit message is cut with ellipsis

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