- Dec 02, 2018
-
-
- Nov 10, 2018
-
-
Romain Bignon authored
-
- Oct 09, 2018
-
-
rdate and date of some transactions are way too far, like 10 years of difference
-
- Sep 16, 2018
-
-
Sometimes the BRED website enters an infinite loop so we must catch these exceptions and stop the loop, however some customers have a lot of transactions and it seems 30000 was not enough. Closes: 20219@sibi
-
-
Weboob and the backend need ids to be of string type, otherwise it causes crashes in the backend during synchronisations when trying to fetch and match accounts/transactions. Closes: 17791@sibi
-
'022' corresponds to Livret d'épargne populaire, which is TYPE_SAVINGS.
-
Sometimes the customer's email is hidden in the JSON and the key is called emailPartOffusque instead of emailPart. To prevent KeyError I added a condition to verify that emailPart is in the response content before assigning the email value. Closes: 19908@sibi
-
- Aug 18, 2018
-
-
My recent commit 2aacd2bf fixed rdates from transaction labels for type_card and type_withdrawal, however some untyped transactions may also contain dates in their labels and their rdate must be fixed too. Closes: 6085@zendesk
-
We first set rdate for all transactions and then apply the parse() method to replace the rdate if we find a date pattern in the transaction label (therefore, for transaction of type_card and type_withdrawal). Closes: 6085@zendesk
-
To make the blackbox work. I did not write the code, I just adapted it. It needs to use DictElement and co, but I am afraid to break something by doing this.
-
-
- Jul 29, 2018
-
-
-
refs #5867@zendesk
-
The Life Insurances were not scraped on the BRED website. This is now implemented along with the respective investments. The investments details are not complete but from the BRED website we can at least scrape the various types and amounts of investments. Closes: 5690@zendesk
-
- Jun 09, 2018
-
-
-
When an account is named 'Compte à vue', it is now a checking type account. Closes: 5269@zendesk
-
- Mar 31, 2018
-
-
- Feb 04, 2018
-
-
Closes: 4033@zendesk
-
- Dec 03, 2017
-
-
-
-
The bred connections was encountering 401 errors recurringly This patch fix authentication and refactor history fetching to adapt the new endpoint characteristics.
-
- Nov 18, 2017
-
-
-
-
-
Closes: 422547@redmine
-
-
- Sep 20, 2017
-
-
Florent authored
-
- Sep 10, 2017
-
-
- Aug 30, 2017
-
-
- Jul 08, 2017
-
-
The certificate changed and NSS doesn't always seem to accept it, force it. A previous patch on regular bred website added "coming" argument to get_history, which didn't exist, so add it.
-
Coming transactions have a random id (uuid), so the id should not be parsed. And they should be separated from history.
-
-
- Apr 01, 2017
-
-
-
basic port without declarative code
-
- Mar 11, 2017
-
-
- Jan 28, 2017
-
-
Just ignore these accounts, the duplicates are likely unusable on website too anyway
-