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

l10n_it_intrastat: modifica nome variabili #2510

Open
3 tasks
TheMule71 opened this issue Nov 15, 2021 · 2 comments
Open
3 tasks

l10n_it_intrastat: modifica nome variabili #2510

TheMule71 opened this issue Nov 15, 2021 · 2 comments
Labels
12.0 14.0 16.0 enhancement no PR yet 🫤 no stale Use this label to prevent the automated stale action from closing this PR/Issue. triaged

Comments

@TheMule71
Copy link
Contributor

TheMule71 commented Nov 15, 2021

amount_euro = invoice_currency._convert(
amount_currency,
company_currency,
self.invoice_id.company_id,
fields.Date.today())
statistic_amount_euro = amount_euro
res.update({
'amount_currency': amount_currency,
'amount_euro': amount_euro,
'statistic_amount_euro': statistic_amount_euro})

Sebbene sia pressoché una questione estetica, il codice si basa sull'assunzione implicita che la valuta della company sia euro, sarebbe meglio prendere direttamente euro e usare quello per le conversioni, oppure cambiare nome alle variabili per essere un po' più agnostiche. Vd. anche

#2228 (comment)

  • 12.0
  • 14.0
  • 16.0
@sergiocorato
Copy link
Contributor

Concordo che se si dà per scontato che siano Euro, sia meglio prendere direttamente la valuta ignorando l'impostazione dell'azienda.
Per correttezza sarebbe da far apparire un errore quando l'utente tenta di inserire una valuta diversa dall'Euro all'azienda se sono installati i moduli intrastat.

@primes2h primes2h changed the title [12.0][14.0] modifica nome variabili l10n_it_intrastat: modifica nome variabili Jan 24, 2022
Copy link

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 23, 2024
@TheMule71 TheMule71 added no stale Use this label to prevent the automated stale action from closing this PR/Issue. and removed stale PR/Issue without recent activity, it'll be soon closed automatically. labels Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
12.0 14.0 16.0 enhancement no PR yet 🫤 no stale Use this label to prevent the automated stale action from closing this PR/Issue. triaged
Projects
None yet
Development

No branches or pull requests

4 participants