-
Notifications
You must be signed in to change notification settings - Fork 482
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
Example coolblue #428
Example coolblue #428
Conversation
What JSON output would you expect for this invoice? Basic lines should probably look like:
I don't know however what to do with those extra lines. Should we have something like
? |
Here's the result from my previous template / code. I like your version better, as the serial number could be captured in a separate field. The challenge is, the thuiskopie line. coolblue2 output
coolblue3 output
|
I see, this one is a real headache. It seems we need to make This is the best solution I could came up with so far:
Lines output:
|
@bosd: what is your opinion on those templates & outputs is provided in my 2 above comments? Are they sufficient? Or do you have any better ideas? |
97c9289
to
7b89df2
Compare
The compare is failling, duno yet what is causing the difference between my local system and the repo. |
4feccea
to
abfea06
Compare
Tests keep failing.
For this file, the Is this one failling because of this logger line? |
49b4f36
to
09a3458
Compare
previous statement was wrong. |
You can also input an array of line patterns. So, simply enclose your strings in square brackets and separate them with a colon: For example: (...) This results in each example going into one line item, as follows: (...) My problem was that I had to extract data from lines that spanned across five actual lines. I searched for a while and debugged invoice2data until I reached this point |
These invoices have 2 different types of lines.
The problem is in the line
Incl. Thuiskopieheffing: Thuiskopie €3.50 1 21% € 4,24
where the content of the column
prijs per stuk
has moved to the front.Made a template in the past, which could parse both the regular lines and the custom line as mentioned above.
Yet, the current code cannot support this kind of syntax.
Converted it to the current syntax. But had to comment out the second line rule.
If the second line is not commented out, there is the following error.
@rmilecki Do you have any idea how to parse both line layouts?