- Sep 09, 2020
-
-
- Aug 26, 2020
-
-
-
-
This is a 'Livret First'
-
- Jul 02, 2020
-
-
One connection has an exact card's duplicate. This is a blocking state by default. Set ignore_duplicates in the related page's Elements solved the problem.
-
If not the ID will be the main account ID and would an raise "There are two objects with the same ID" error.
-
- Jun 03, 2020
-
-
-
Some transactions have wrong dates like 18.33.2019 so we better check if the digits are actually between 1 and 31 (for the day) and 1 and 12 (for the month) before parsing, otherwise Transaction.raw will crash. Closes: 19557@zendesk
-
- May 07, 2020
-
-
-
-
-
Closes: 17977@zendesk
-
The BGPI space was not handled yet on the new website. Also typed some related accounts (VENDOME). Closes: 18736@zendesk
-
- Apr 08, 2020
-
-
Somes loans are present twice so it's important to type them correctly to avoid 'there are two objets with the same ID' errors.
-
-
- Mar 18, 2020
-
-
There is only one browser now, no need to keep the /api folder. Also added a comment on how we build the BASEURL from the website choice.
-
The dateValeur used for the date is unstable and sometimes irrelevant. So instead we use dateOperation for the date of transaction (which is always the date used by the website). This modification requires some modifications on the rdate which used to be compared to the dateValeur.
-
- Mar 05, 2020
-
-
For pro that use api rdates are build from Transaction.raw but string used can be misleading sometimes. This would cause the whole account to be in error. Now sending NotAvailable based on same date tests made in the backend Closes: 42109@sibi, 16864@sibi, 16023@zendesk, 16612@zendesk, 16947@zendesk
-
- Feb 12, 2020
-
-
Summary transactions come from the parent checking account and their dates have no time, whereas card transactions had a time, making the comparison with sorted_transactions() crash. Since the times are just '12:00:00 AM', we exclude them in order to fix iter_card_history.
-
DateTime for date is removed because the time is always 12:00:00 AM. If the rdate is not found with the patterns, we try to set it to dateOperation if dateOperation is before dateValeur.
-
-
- Jan 30, 2020
-
-
Reformatting was done with: for f in modules/cragr/**/*.py do ./tools/hooks/yapf-wo-imports.py -i yapf \ --style tools/hooks/style.yapf "$f" done For yapf to give pretty code, some manual "hints" were added. Example 1: re.compile("some regex around 120 chars") was reformatted to: re. compile("some regex around 120 chars") but it can be improved by forcing it to separate param and then calling yapf: re.compile("some regex around 120 chars",) Example 2: if long_condition or foo(foo) or bar(bar): was reformatted to: if long_condition or foo( foo ) or bar(bar): but it can be improved by surrounding the whole condition in parentheses, and then calling yapf: if (long_condition or foo(foo) or bar(bar)):
-
Some text replacements can be done using CleanText, avoid some chained dict.get(), and avoid a nested dict.
-
Closes: 15776@zendesk, 15777@zendesk
-
- Jan 08, 2020
-
-
-
-
Currently, account labels have no informations on who the accounts belongs to. For Organization connections with accounts belonging to different organization this caused multiple accounts with the same label but no way to identify which organization it belonged to.
-
Somme patterns for matching rdates from transactions labels weren't strict enough, for exemple : ^(?P<category>PRELEVEMENT) (?P<text>.*) (?P<dd>\d{2})\s(?P<mm>\d{2})\s(?P<yy>\d{4}) .* matched PRELEVEMENT TEXT TEXT (YYYY MM DD YYYY MM DD) ^(?P<category>PRELEVEMENT) (?P<text>.*) (?P<dd>\d{2})-(?P<mm>\d{2})$ matched PRELEVEMENT TEXT TEXT MM-YY Both were made stricter as to avoid these unwanted matches that would crash the date parser.
-
- Dec 18, 2019
-
-
Get rdate from label of transactions, the value from the json is often wrong.
-
- Oct 01, 2019
-
-
Added MARKET type for "INTEGRAL C.T.O" netfinca accounts Changed cragr account type for "ACCOR MULT" to TYPE_MADELIN Added missing account types to cragr (regions+api)
-
- Jul 18, 2019
-
-
- Jul 05, 2019
-
-
Some perimeters seem to have no main account (or no account at all) so we must check this before calling get_main_account(). Closes: 11808@zendesk
-
'FLORIANE 2' as TYPE_LIFE_INSURANCE (cragr régions) 'CEL2' as TYPE_SAVINGS (cragr api) 'LIVCR' as TYPE_SAVINGS (cragr régions) ‘INTEGRAL PEA’ and ‘COMPTE PEA-PME’ as TYPE_PEA (submodule netfinca) Closes: 11364@zendesk
-
-
- Jun 17, 2019
-
-
Some accounts with transactions in dollars do not contain the regular JSON keys for the transactions labels, only the 'libelleOperation', therefore we must set default values to avoid ItemNotFound errors. Closes: 10924@zendesk
-
Loans must be typed correctly to avoid account ID duplicates. Closes: 39128@sibi
-
Cards with the value "5" for codeSituationCarte key are absent on the website, we skip them. Closes: 11331@zendesk
-
Firstly some revolving (or all) were skipped because the id were not changed like other loans. Moreover the id category were not found, we handle the json path to get it. Necessary in order to get the balance. Closes: 39362@sibi 10886@zendesk 11205@zendesk 10924@zendesk
-
Closes: 11230@zendesk, 11336@zendesk
-
If the OWNER_TYPE is not recognized, the profile will not be scraped.
-