-
-
Notifications
You must be signed in to change notification settings - Fork 133
[18.0][IMP] l10n_fr_siret_lookup: Conditionally check VIES and force VAT + tests #682
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
base: 18.0
Are you sure you want to change the base?
[18.0][IMP] l10n_fr_siret_lookup: Conditionally check VIES and force VAT + tests #682
Conversation
|
Built on top of #681 |
|
Hi @alexis-via I would appreciate your feedback on this proposal when you can spare a few minutes ! |
7033cd2 to
6a9ac66
Compare
cefd8bd to
7fd35fd
Compare
|
Thinking again about this module how to request new validation from VIES service, I started another module not directly related to this one, since the issue with max request happens also without this module installed. |
|
This PR has the |
7fd35fd to
a9dc971
Compare
|
Hi @remi-filament , any chance to rebase to trigger CI/CD and go to merge |
Rename wizard obj to fr.siret.lookup Test on stdnum version number
Currently translated at 97.7% (43 of 44 strings) Translation: l10n-france-14.0/l10n-france-14.0-l10n_fr_siret_lookup Translate-URL: https://translation.odoo-community.org/projects/l10n-france-14-0/l10n-france-14-0-l10n_fr_siret_lookup/fr/
'codedepartementetablissement' is not always set (in particular for companies in Corsica), so we now only use codepostaletablissement
Odoo 16 depends on both requests and python-stdnum, so there's no need to specify those dependencies. Besides, [python-stdnum is pinned to 1.16][1]. Thus, when applying OCA/oca-ci#66 locally, the constraint failed. OCA addons should work with the dependencies pinned upstream. [1]: https://github.com/odoo/odoo/blob/fe4d8e8014e50d4335e0a8b052b5098f3a79bcec/requirements.txt#L48 @moduon MT-4520
a9dc971 to
eadc898
Compare
|
Done @flotho although I am still looking for a replacement regarding your comment here : #680 (review) |
As proposed in #680 (comment)
I have added a couple of things on this module :
This is also linked to #591 trying to workaround the MS_MAX_CONCURRENT_REQ raised by VIES service most of the times when checking for FR VAT.
Note that if VIES returns that VAT is invalid, the VAT is emptied in any scenario (independent of value of force_vat_siret_lookup)
We could go a few steps further, for instance by showing the validation status on partner form view and either allowing to rerun the check or to be handled by cron.