Also:
- Use context managers for file opening/closing in tests
- Changed use of deprecated `BadZipfile` exception
- Removed debugging code left by mistake
* correctly parse entries with multiple transactions
Our bank does it. Care has been taken not to break cases where
Ntry/NtryDtls/TxDtls isn't used: if any piece of information isn't found
on these nodes, the matching information from the Ntry is used. Most
often the entry has a sum or a summary and the transaction details are
more precise and specific, so it makes sense to use their contents
rather than its.
* more complete unit tests for camt parser
This checks the whole output data of the parser against its expected
output.
* add a test case that checks TxDtls decoding
* special case for Ntrys without TxDtls
* CO-12 - Date Import BVR
* FIX tests
* CO-1232 Fixed issues with CAMT parser tests
Message was not taken from AddtlNtryInf element, if not part of details.
Not sure wether it actually can be part of details (NtryDtls element), but this change least intrusive.
Update version to 11.
Get balance start even if currency code is already set.
Add SNS test, add header_lines parameter in parse file.
Update code, add pre process datafile to change from different format to only one, statements as dict starting with {4:..}, split file to import multiple statements at once, the check of date of statement import not implemented, be carefully not to import twice the same statements.
Update flake.
Add wrong file.
* Remove the code that matches partners, which is wrong and cannot work
* Better 'name' on bank statement
* Move from models directory to wizard
* Remove demo data to tests
* Use latest version of ofxparse from github
Maxence Groine
OCA Transbot
Alexis de Lattre
eLBati
ecino
Emanuel Cino
david wulliamoz
Louis Bettens
Stefan Rijnhart
Holger Brunn
Ronald Portier (Therp BV)
Rudolf Schnapka
Pedro M. Baeza
Stéphane Bidoul
OCA Git Bot
Fekete Mihai
Alexis de Lattre
Sylvain LE GAL
Ilyas