- Oct 11, 2018
-
-
When we face an error at login, bnp gives us a code. This code's signification is explained on at documentation page. This commit gets the message directly from the website.
-
bnp now ask the new password to be different from the past 2.
-
- Oct 09, 2018
-
-
Do not use AddRecipientError for user error anymore Use AddRecipientBankError instead and use 'assert' for program error case
-
- Sep 17, 2018
-
-
Romain Bignon authored
This reverts commit f65830ba.
-
- Introduce more swear words to represent the diversity of the English language - Upgrade outdated insults - Only wish harm on objects (though webdevs barely qualify as human)
-
- Sep 16, 2018
-
-
- Aug 22, 2018
-
-
For some reason the pages.py file contained tabs instead of spaces, I replaced all the concerned lines and re-tested with BNP connections to verify that everything works and that the file passes the pyflakes3 test.
-
- Aug 18, 2018
-
-
The BNP module did not scrape the "Assurance Vie" space yet, which may contain additional accounts that are not included in their API. Among those we can find Life Insurance, Capitalisation contracts and PERP accounts, and maybe more. I also implemented the iter_investments() method for this space, however the domain does not seem to display any kind of transaction history for these accounts. Closes: 5016@zendesk
-
- import unicode_literals in each Python module - import weboob's basestring compat - xrange -> range - tested on 90 connections, 1 for each API
-
- Jul 29, 2018
-
-
Closes: 9334@sibi
-
A recurring problem with bnporc is that sometimes you may not have the good transactions list. It may be truncated a lot. For example, from 50 transactions, you had only 5. Because of that, in the backend some transactions become deleted because of one update with the bad transactions. I tried to fix it by copying the website, since you never had bad transactions on it. First, I changed the 'typeReleve' from 'Comptable' to 'Previsionnel' because it is the only type the website is using. And I added some parameters to the history request. The same ones are used to go on the transaction page and to get the json data. I tested a lot on connections, knowing the right and the wrong history state. Since I applied the patch, I had not once the wrong state. Closes: 5663@zendesk Closes: 6219@zendesk Closes: 6225@zendesk Closes: 6229@zendesk Closes: 6115@zendesk
-
In some case, you may have only one market type account. If so, the website does not show a page with the list of one account but directly the details of this account. Most of the time, getting the number in the account label is enough to recognize it in the iter_accounts. But sometime you have custom account label, so it is not enough. That is why the entire account name is retrieved. Closes: 13125@sibi Closes: 12518@sibi Closes: 13576@sibi Closes: 12610@sibi Closes: 12871@sibi Closes: 11832@sibi Closes: 11912@sibi Closes: 11913@sibi Closes: 11867@sibi Closes: 11750@sibi Closes: 11749@sibi Closes: 11580@sibi Closes: 11715@sibi Closes: 11714@sibi
-
Closes: 6189@zendesk
-
Closes: 10674@sibi
-
My precedent MR had an error when an account doesn't have number in the label. The fix allows the account to have number. closes: 750661@redmine
-
Closes: 4907@zendesk
-
Add a connection to the "Placements" page, and scrapping on the HTML pages. For this it was necessary to take a token and a specific account ID to reach the invest page. closes: 5078@zendesk
-
Problem 1: The rdate found in the raw can be truncated. So it is ignored. Problem 2: The date field can be empty. So the coming is ignored. Closes: 870@sibi Closes: 4470@sibi Closes: 6436@sibi Closes: 7235@sibi
-
- Jun 09, 2018
-
-
-
* getting rid of no purge, replacing with updated softcap * use sorted_transactions because transactions were not always sorted by rdate after date
-
sometimes the advisor has no email and therefore the connection crashed when parsing json page.
-
- May 05, 2018
-
-
-
Add parameter 'exec_date' in prepare_transfer Delete date checking in transfer summary because it's also in CapBankTransfer Closes: 586759@redmine 586759@redmine 586752@redmine
-
-
- Apr 15, 2018
-
-
- Mar 31, 2018
-
-
-
-
rearrange get profile code Some pro connections don't have profile page Raise NotImplementedError in this case Closes: 587998@redmine
-
-
On history page, load coming card details allow to get card number to sort coming and history transactions Closes: 4544@zendesk
-
-
-
- Mar 03, 2018
-
-
Change description parameter into message parameter to show "wrong code" error message to users
-
Move recipients, transfers and get_advisor source code from BNPPartPro to BNPParibasBrowser in order to share features with hellobank.
-
In transactions main JSON page, there are 'transactions' and 'coming'. It's not necessary to go on coming transactions details page from transactions JSON to get card number because there is a special page for coming transactions with card number. Closes: 558478@redmine
-
Decimal number key for amount can be 'nbDec' or 'nb_dec' Closes: 556862@redmine
-
- Feb 04, 2018
-
-
-
Some not card transaction might have "FACTURE CARTE" in raw Closes: 490732@redmine
-
- Jan 14, 2018
-
-