- Apr 11, 2021
-
-
Romain Bignon authored
-
Romain Bignon authored
-
- Apr 04, 2021
-
-
- Mar 24, 2021
-
-
- Feb 26, 2021
-
-
The error message appears when the user is trying to do a transfer of the amount of a check that was received in the 10 previous days.
-
`condition()` methods are usually defined at the beginning of an item processing. It was all the way down which can confuse the readers.
-
Split sub-transactions are filtered out by `condition`. However the current XPath to get the `obj_amount`, matches multiple element (the global transaction and the split sub-transactions) causing an AssertionError using the `CleanDecimal.French` filter. To solve this, we first check if the transaction is split. If it is we only use the first matched element (which corresponds to the transaction's total amount)
-
-
Usually, with Boursorama, otp was only encountered when adding recipients. But, an otp could be needed at confirmation step for some transfers (ex. big amounts, unregistered foreign bank accounts). In addition, a check was added to ensure that a transfer is really confirmed before returning successfully from execute_transfer.
-
- Feb 20, 2021
-
-
Romain Bignon authored
-
- Feb 12, 2021
-
-
There's a new insurance '/assurance/habitation' that was not filtered out in iter_accounts. These insurances are all located under this route 'assurance/', so we can use this as a condition.
-
While fetching accounts, we can get disconnected. The redirect URL was not handled, so we would never try to relogin to the website.
-
Finding ownership for accounts only makes sense if there are ownerless accounts. I added a condition to make sure we are not sending the request to find potential owners if there are no ownerless accounts.
-
Caching accounts is a bad idea, it wasn't abused in the module so this rework involves only some minor changes.
-
Since we use `from __future__ import unicode_literals`, we don't need to specify the prefix for unicode strings anymore.
-
Using Async isn't considered best practice, this commit replace Async logic by fill_account
-
Without this fix, the iter_document will crash because of duplicate id. Sadly there was no reliable webid to base on
-
it was useless to give the BASEURL with the open
-
iban has no proper date since the given date is the date at which we want to download the document
-
-
There seems to have no pagination to be handled, I tested on an account existing since 2014, with 75 statements and there was no pagination.
-
for this kind of documents, only a month and year are given
-
multiples pages have exactly the same url ( they seems to be pages containing brut information, but they don't have the same format.) To avoid this conflict, a proper iban page detection has been added
-
The CleanText was just getting the label...
-
The first line is just some kind of header to tell the user to select an account
-
- Fix URLs without raw strings - Add CapDocument capability * Bank statements * Bank Identity document - Add defaults to BankStatementsPage.submit_form()
-
- Jan 27, 2021
-
-
For the labels, we are fetching an <a> tag, except that some invests have no link so we were retrieving invests with empty labels. We now handle <a> or <strong> cases with a Coalesce. Codes were handled with IsinCode & code_types with IsinType. Used Base filter instead of ugly filter()(self)[0].xpath().
-
- Jan 09, 2021
-
-
-
-
hydrargyrum authored
-
For some connections (approx. 3% total), life insurances link are broken on boursorama's website. This leads to unhandled 404 error which affects adding new connection and synchronizing existing ones. This commit provides a quick fix by catching 404 error in 'iter_accounts' for life insurance accounts and skipping them in that case.
-
-
- Dec 26, 2020
-
-
For some errors, like "insufficient balance for transfer", the error has a different class, and the title is no here, so we can not use it for is_here.
-
- Dec 11, 2020
-
-
In the "suivre vos virements" section of Boursorama, The "bank_name - Iban" line is sometimes empty. This could be the case of bank initiated transfers (to life insurance for example) or for a transfer to a previously registered recipient that was removed.
-
In some cases, there could be an EstimateFees page that could appear in the transfer wizard before the transfer confirmation page. I encountered this case with a special "CEFP" account that shows this page for giving the estimation of the estimated annual "management" fees for the additional amount, despite the transfer fee still being of 0 euro.
-
-
Fixes the following error: "Ce formulaire ne doit pas contenir des champs supplémentaires." That could occur when trying to transfer from an account that is limited to existing recipients (ex.: livret A).
-
- Nov 27, 2020
-
-
Some connections now have loan rates using the '1.123' format so we must handle both cases (French and SI) otherwise the rates are not fetched at all.
-
cfep stands for Compte d'Epargne Financière Pilotée.
-
