Rafał Miłecki
Rafał Miłecki
@gregoribic: can you provide update on this, please?
You need release 0.3.6 or newer for the `fields:` syntax support in YAML. Can you re-test with 0.3.6, please?
@jintaogao was correct, thanks @jintaogao for your help here
> if legacy: > result = list(set(result)) This is used for legacy YAML syntax only. It has to stay that way for backward compatibility. > In my case, result =...
> File "/home/reikred/src/invoice2data/src/invoice2data/extract/invoice_template.py", line 178, in extract > res_find = re.findall(v, optimized_str) This particular error was caused by using **new** field syntax with **old** version of `invoice2data`. I suppose you...
Any special handling of extracted data **based on fields names** is not a really good idea. It's not flexible enough. It doesn't allow specifying all details on how data should...
Right now `lines` parser supports only one set of rules like: ``` fields: lines: parser: lines start: Item\s+Discount\s+Price$ end: \s+Total line: (?P.+)\s+(?P\d+.\d+)\s+(?P\d+\d+) ``` Whenever I deal with company that randomly...
The error message says `No template`, which means not a single template was found that would match your invoice. Matching is done by looking for strings specified in the `keywords`....
I have & use **trivial** `Flask` based web API, I'll try to clean it up and share next month.
I'm all for it. My YAML experience comes from Linux kernel which uses YAML for defining syntax for Device Tree bingings. It's absolutely great for validation. FWIW Linux kernel uses...