Closed not7cd closed 1 year ago
That's an odd format indeed. With regards to fixing it, I can think of two options:
tags.StatementNumber.pattern
so it matches this dataThe pre-processor is the cleaner solution, but I think patching the pattern might be an easier solution here.
This issue has bitten me again. How can I monkey patch this?
Hi, I encountered error while parsing statements from polish bank.
It seems that they are also inconsistent with their own spec which says that StatementNumber follows this pattern
While actual data privdes this
Can I somehow bypass this, or maybe define my own tag parsers?