Monday, June 23, 2025
1 change · saas-18.3
Resolved issues and error corrections
Users configuring bank reconciliation matching rules will now see a clear error when a search pattern is written incorrectly. This prevents silent failed matches or unexpected crashes, making setup issues easier to identify and fix.
Original PR description
Before, with some errors in the regex search in the different statement line attributes, the search would just return 0, when the regex was just badly written, without giving any hint to the user. Now the method will raise an user error telling the user that the regex is badly written instead of returning 0.0 or a traceback (AttributeError was not handled). Examples of previously failing regexes: - "([^\d]*)" -> AttributeError - [\d,]* -> IndexError (was already handled by https://github.com/odoo/enterprise/pull/84284) - ValueError shouldn't arise anymore with that same PR, but better safe than sorry