Merge lp://staging/~akretion-team/banking-addons/bank-statement-reconcile-61-ref-base-import into lp://staging/banking-addons/bank-statement-reconcile-61
Proposed by
Benoit Guillot - http://www.akretion.com
Status: | Merged |
---|---|
Merged at revision: | 81 |
Proposed branch: | lp://staging/~akretion-team/banking-addons/bank-statement-reconcile-61-ref-base-import |
Merge into: | lp://staging/banking-addons/bank-statement-reconcile-61 |
Diff against target: |
507 lines (+94/-74) 5 files modified
account_statement_base_import/parser/file_parser.py (+9/-8) account_statement_base_import/parser/parser.py (+30/-26) account_statement_base_import/statement.py (+47/-31) account_statement_base_import/statement_view.xml (+1/-2) account_statement_base_import/wizard/import_statement.py (+7/-7) |
To merge this branch: | bzr merge lp://staging/~akretion-team/banking-addons/bank-statement-reconcile-61-ref-base-import |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Guewen Baconnier @ Camptocamp | code review, no test | Approve | |
Holger Brunn (Therp) | code review, no test | Approve | |
Review via email: mp+159104@code.staging.launchpad.net |
Description of the change
In this merge proposal, I submit some changes in the module account_
- Fix argument keys_to_validate in the init of the file_parser
- add the possibility to force the dialect for the csv dictreader
- fix the field : import_type of the class account_
- remove sapce at the end of lines due to my IDE
- fix typo in the name of the method :prepare_
To post a comment you must log in.
"remove sapce at the end of lines due to my IDE"
Can you remove this option from your IDE please?
You removed the mutable in (l.11) the keyword argument, which is correct. But I don't think the change of the line 52 is fine. I would prefer to initialize `self.keys_ to_validate` to an empty list when the argument is None. Thus, the change is backward compatible and you don't need to verify the attribute everywhere it could be used.
l.78: the del on the kwargs could fail with a KeyError
l.318: fixing the typo errors in method names is fine, but I think you should ensure backward compatibility at least for public methods, keeping the old method which delegate the call to the new one (ideally with a warning).
Thanks for your MP