- Jan 14, 2018
-
-
Closes: 477593@redmine
-
-
And JSONDecodeError doesn't exist in python2
-
Here is the fact. Before, we were creating unique ID from date, row, and others informations that were disponible in the website. Transaction's id aren't mandatory, and it was pretty ugly. Adding to that the fact that we recently got a case where there was two exactly similar transactions, causing a crash, we deceided to delete it.
-
Sometimes they are some duplicates transactions with same date / hour / store name
-
-
-
-
-
-
-
-
- Dec 30, 2017
-
-
-
-
more
-
-
-
-
-
now the pattern will match directly fr iban Closes: zendesk@3825
-
However, the wrong otp still isn't detected properly
-
-
URL in iframe for "pret" doesn't match pattern "/comptes_contrats/sans_"
-
closes : 3811@zendesk
-
closes: 3812@zendesk
-
-
We should not create Account objects for cards, and the history of these cards must be returned on checking account. We can do some guessing by looking at the history of an account and looking if the transactions have spread debit dates or only once per month.
-
On the site, the card coming is on card page, but card history is on checking page. Before, the history on cards was not returned, but it's possible to find on which card is a history transaction, so we now yield such transactions on the related card account instead of checking account. However, if the site doesn't show the card if there are no coming transactions, so in this case the history will not be returned because the card Account object cannot be created.
-
Same "compte de dépôts" on LCL website are visible on AccountsPage and BoursePage In BoursePage, there are 2 columns: "Solde espèce" and "Valorisation titres" Column "Solde espèces" = balance on AccountsPage + overdraft authorization Column "Valorisation titres" = value-creation on "compte de dépôts" equities Boobank has to get only "Valorisation titres" column for market accounts because liquidities are already in checking accounts
-
Closes: 475624@redmine
-
-
-
-
Closes: 3730@zendesk
-
-
-
The regexp we made with next_month is great but we added something to the card_page even if the card id was wrong. Closes: 3594@zendesk
-
-
Closes: 3634@zendesk
-
-