- Apr 11, 2021
-
-
Romain Bignon authored
-
Romain Bignon authored
-
- Apr 04, 2021
-
-
- Jan 09, 2021
-
-
JS filenames are randomized and must be fetched. One of the random strings has been moved from a <script> tag to another js file that we need to fetch.
-
hydrargyrum authored
-
- Oct 28, 2020
-
-
We can sometimes get a "request rejection" as a response from myedenred. We now catch them to retry the request.
-
Tells the end user that his account is locked so he can do something about it.
-
Previously, the xpath set to fetch the error message was also taking some non visible error message from the browser, useless for the user
-
- Sep 23, 2020
-
-
The login URLs changed and once we reach login page there is now a `<form>` instead of the former JSON login system.
-
- Aug 26, 2020
-
-
The refresh token expires at ~24h. We repeat the login procedure from the beginning to avoid reporting a false wrongpass.
-
On first login, we have to solve a CAPTCHA to login, and then MyEdenred gives an access_token and a refresh_token. But unlike previous code, on subsequent logins, we can reuse the same access_token, rather than solving the CAPTCHA again. And when the access_token expires, we can simply use the refresh_token to get a fresh access_token, rather than solving another CAPTCHA. By using OAuth2iPKCEMixin, we leverage its token management.
-
- Aug 07, 2020
-
-
Sometimes after getting the captcha from anti-captcha.com the MyEdenred website returns the error 'Invalid captcha response'. I have added a condition not to raise a false wrongpass and try again the captcha
-
change the regex of the login to avoid the space character because the login is use in the url, and you can have a %20 in the url.
-
-
-
There are some accounts on which the first requests fails with a 500. Reducing the page_size avoids these crashes. But there are some accounts which fails on the 3rd or 4th requests, probably because there is no more transactions to fetch. For these ones we consider a ServerError ONLY if there was no fetched transactions and if the error is similar.
-
- Jul 15, 2020
-
-
ast.Constant was added in 3.6 so the module will crash for versions 3.5.X (with X >= 1)
-
- Jun 03, 2020
-
-
Closes: 17801@zendesk 64331@sibi
-
- May 10, 2020
-
-
- May 07, 2020
-
-
Sometimes there is value like client_id:'a["default"].EDCId' returned in the json, since we do not need the client_id, and it's not a client_id we can delete this kind of value closes: 69174@sibi, 69176@sibi
-
- Feb 12, 2020
-
-
Romain Bignon authored
-
Romain Bignon authored
-
-
-
- Jan 30, 2020
-
-
Closes: 51292@sibi 15307@sibi 15507@sibi
-
-
Some transaction have different pattern than usual, eg: "1426405" instead of "NESTOR-X RUE NOMDERUE,00000,VILLE" Some of those different transactions also have a "reason" which contains the missing name of where the order was passed. Closes: 53340@sibi
-
- Nov 09, 2019
-
-
The format of the JSON we were looking for changed format. Now we directly match the JSON with at least one key in it, instead of matching what was before the JSON. Closes: 50771@sibi
-
The website completely changed. Applied those changes to the module. Closes: 49407@sibi 13936@zendesk 13989@zendesk 14097@zendesk
-
- Sep 11, 2019
-
-
I've changed the "OperationType" in the POST request to "default" I've blocked the "transaction refusée" and "transaction en cours de traitement". closes : 9105@zendesk
-
- Jul 05, 2019
-
-
- Apr 20, 2019
-
-
When people have more than one accounts, accounts information are not available from the main page. Both behaviors are now handled.
-
- Mar 16, 2019
-
-
Romain Bignon authored
All copyright holders have given their consent.
-
- Feb 27, 2019
-
-
Romain Bignon authored
-
- Feb 24, 2019
-
-
Romain Bignon authored
-
- Jan 29, 2019
-
-
- Jan 06, 2019
-
-
Romain Bignon authored
-
- Jun 03, 2018
-
-
hydrargyrum authored
-
- Jan 23, 2018
-
-