You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, thank you so much for this tool and the wonderful exception messages you provide in this tool!
They are so good, in fact, that I was almost able to construct an EDI mapping from just the exception messages alone (they do a wonderful job of hinting at what to do next).
To that end, it would be great if, when the number of fields is less than there should be for a segment, to add information about what the current field delimiter is. That way, the user can add the required amount of field delimiters to move on to a successful parse or, in the worst case, the next error message they can use to continue.
This idea would be great to add for any location in parsing where a delimiter is required.
First off, thank you so much for this tool and the wonderful exception messages you provide in this tool!
They are so good, in fact, that I was almost able to construct an EDI mapping from just the exception messages alone (they do a wonderful job of hinting at what to do next).
To that end, it would be great if, when the number of fields is less than there should be for a segment, to add information about what the current field delimiter is. That way, the user can add the required amount of field delimiters to move on to a successful parse or, in the worst case, the next error message they can use to continue.
This idea would be great to add for any location in parsing where a delimiter is required.
Here's the exception in question:
smooks-edi-cartridge/edi-sax/src/main/java/org/smooks/edi/edisax/EDIParser.java
Line 725 in dc705c2
Again, thank you! :)
The text was updated successfully, but these errors were encountered: