-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
re #30: Add a parser for transaction details. #43
Conversation
Very nice work, thanks! :) Before I can merge it I need to make sure everything is properly tested so that can take a little bit of time but I'll get on it. |
This implementation looks like it's for German banks. Other countries format the description differently. See "Codes used in field 86" on page 10 for various country specific codes: See "Structured Field 86" on page 7 and examples in Appendix C on page 13 for how it's formatted in the Netherlands: It could be included specifically as the German variant but not added by default. Other variants could be added and maybe some common code could be reused. There might even be an 'auto-detect' version that could be added at some point. Note: I'm not the maintainer of this project, I'm just giving an opinion. |
Thanks for the research Ben, I wholly agree.
|
…t unchanged if introspection fails.
Hi there, I changed the parsed to introspect |
Since this code will mostly likely be used for other countries as well, it would be nice if you could use English instead of German in the |
Done. Since English is a foreign language to me, feel free to change some of the translations if you find them not accurate. |
just a little update, I'm still working on merging the code in and getting everything tested :) |
For some reason the tests are working for me locally but not within tox or travis... still working on getting everything working |
FWIW: The parser we developed internally is now available publicly at https://github.com/pretix/pretix-banktool/blob/master/pretix_banktool/parse.py Feel free to take it as inspiration or ignore it. We find it especially convenient as it is able to join references that have been split into multiple lines back into one useful string value. |
That code looks quite nice, I'll see if I can modify it to fit :) |
As announced in #30 here is a suggestion how to implement the parser.