allow custom (per-market) regex config

smallstepman commented 2 years ago

Proposed change allows the user to provide following the config.yml

language: deu

receipts_path: "data/txt"

results_as_json: false

markets:
  Colruyt:
     - colruyt
     - Colruyt
  Migros:
     - genossenschaft migros
  Metro:
     - vetro
     - metro

sum_keys:
  - summe

sum_keys_metro:
  - something
  - sumthing

ignore_keys:
  - mwst

ignore_keys_migros:
  - something something

sum_format: '\d+(\.\s?|,\s?|[^a-zA-Z\d])\d{2}'
sum_format_colruyt: '[0-9a-f]*'

item_format: '([a-zA-Z].+)\s(-|)((\d|\d{2}),(\d{2}|\d{3}))\s'
item_format_metro: '[0-9]\s(.*?)\d.()((\d|\d{2})(\,|\.)\d{1,2})\s([A|a]|[B|b])'
item_format_migros: '[0-9a-f]*'

date_format: '((\d{2}\.\d{2}\.\d{2,4})|(\d{2,4}\/\d{2}\/\d{2})|(\d{2}\/\d{2}\/\d{4}))'

meaning, the script will respect custom, per-market configs.

monolidth commented 2 years ago

Great suggestion and implementation @smallstepman!. I really appreciate such contributions. One minor question: in commit: https://github.com/ReceiptManager/receipt-parser-legacy/pull/159/commits/7f05c66309d59f530bfc44c745c72cd20c4ca392 . I have seen that you remove the replace statement. What is the reason for that?

Greetings from Karlsruhe ;)