[18.0][FIX] account_invoice_en16931, l10n_fr_einvocing: Fixes a few errors#22
[18.0][FIX] account_invoice_en16931, l10n_fr_einvocing: Fixes a few errors#22remi-filament wants to merge 9 commits into
Conversation
|
Hi @alexis-via, |
bguillot
left a comment
There was a problem hiding this comment.
beside small change LGTM
Thanks for the fixes !
| @@ -513,8 +513,10 @@ def _fr_ctc_authorization_code_redirect(self): | |||
| siren = self.partner_id._get_siren(raise_if_none=True) | |||
| optional_uri_params = {"superpdp_company_number": siren} | |||
There was a problem hiding this comment.
You can remove this line as it is set in if/else
0f44952 to
a2c6f21
Compare
|
Rebased |
|
Thank you very much for all those fixes. I integrated all of them in my last commit, except the change on the onboarding (I quoted your name in the commit). For some of them, I chose a different solution, in particular for the dependency on l10n_fr_business_document_import : I removed the call on _match_partner, which removed the need to depend on this module. |
|
Thanks @alexis-via I just checked, all my fixes have been implemented but one. See : e191b5e |
|
Yes, I didn't take this patch because I didn't understand it. So, what I understand now, is that you want to be able to test the SUPERPDP onbaording from a company where SIREN is not the SIREN of BurgerQueen nor Tricatel, but any SIREN, and the code would query with a SIREN different than the company's SIREN. Did I understand it correctly ? |
|
Not sure, my issue was that when trying to create a new company with authorization code, Super PDP replied that only SIREN 000000001 or SIREN 000000002 could be created on sandbox instance. Now when trying to connect with Le Filament SIREN + scheme = sandbox, I get the following reply from SuperPDP API : {'error': 'invalid_request', 'error_description': 'No company found with these superpdp_company_number_scheme and superpdp_company_number.', 'state': 'vDcyEKQDiAY45mBmrQCuqpOJyP5h3S'}Maybe I am missing something on this authorization code flow ? |
Hi @alexis-via I have fixed a few errors found while testing.
To ease analysis, I made a commit per fix but I could group them in a single commit if you prefer.
Fixes #4 #19 and #20