[18.0][MIG] account_statement_import_camt: Migration to 18.0 #737
Conversation
xaviedoanhduy
force-pushed
the
18.0-mig-account_statement_import_camt
branch
from
9c01fca to
180fce9
Compare
|
@xaviedoanhduy Can you rebase after merging other PRs? |
Currently translated at 75.0% (9 of 12 strings) Translation: bank-statement-import-14.0/bank-statement-import-14.0-account_statement_import_camt Translate-URL: https://translation.odoo-community.org/projects/bank-statement-import-14-0/bank-statement-import-14-0-account_statement_import_camt/nl/
Currently translated at 83.3% (10 of 12 strings) Translation: bank-statement-import-14.0/bank-statement-import-14.0-account_statement_import_camt Translate-URL: https://translation.odoo-community.org/projects/bank-statement-import-14-0/bank-statement-import-14-0-account_statement_import_camt/it/
Encountered in a Camt.054 statement: currency listed under /BkToCstmrDbtCdtNtfctn/Ntfctn/Ntry/Amt/@ccy
with this commit, the narration field is filled with infos find in the camt file such as reversal indicator, return reason, cheque number, ... before only a banking ref was present. The transaction type field is also filled.
Currently translated at 100.0% (12 of 12 strings) Translation: bank-statement-import-16.0/bank-statement-import-16.0-account_statement_import_camt Translate-URL: https://translation.odoo-community.org/projects/bank-statement-import-16-0/bank-statement-import-16-0-account_statement_import_camt/es/
Currently translated at 100.0% (31 of 31 strings) Translation: bank-statement-import-16.0/bank-statement-import-16.0-account_statement_import_camt Translate-URL: https://translation.odoo-community.org/projects/bank-statement-import-16-0/bank-statement-import-16-0-account_statement_import_camt/es/
Currently translated at 22.5% (7 of 31 strings) Translation: bank-statement-import-16.0/bank-statement-import-16.0-account_statement_import_camt Translate-URL: https://translation.odoo-community.org/projects/bank-statement-import-16-0/bank-statement-import-16-0-account_statement_import_camt/it/
This refactoring will allow using `TestParser._do_parse_test()` method for subclasses defined in inheriting modules. This way, if the new module defines new files in other paths than `account_statement_import_camt/test_files/`, subclasses of `TestParser` will still be able to use the `_do_parse_test()` method for imports and checks. Moreover, a custom value can now be defined for the acceptable differing lines number between inputfile and goldenfile. It will also maintain backward compatibility with the current usage of the method (ie: using only a filename with the assumption of finding it in `account_statement_import_camt/test_files/`). NB: methods are now defined outside of `TestParser` to allow importing them directly, instead of inheriting from `TestParser`.
xaviedoanhduy
force-pushed
the
18.0-mig-account_statement_import_camt
branch
from
180fce9 to
b686079
Compare
hi @grindtildeath, done! |
There was a problem hiding this comment.
Seems like bot commits were merged in some author commits (like unrelated translation files merged in Spanish translation contribution).
Maybe you used the feature in development there? OCA/oca-port#66 (just a guess). I would consider this feature not stable enough for the moment. IMO such commits should be squashed together (bots commits into another bot commit, to not mix contributors & contributions).
If you are unsure, better to preserve the 17.0 history as-is.
hi @sebalix, I don't use the feature you mentioned. I just squash the administrative commits manually following this guide: https://github.com/OCA/maintainer-tools/wiki/Merge-commits-in-pull-requests#mergesquash-the-commits-generated-by-bots-or-weblate |
depends on:
base on:
on this occasion:
bank-statement-import/.pre-commit-config.yaml
Line 20 in a919f9b