ISSUE 227: add parser_settings.debug
flag and enable csv2
reader to optionally inject debug (line) info into record IDR.
#228
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Decided to make the debug flag a global setting in
parser_settings
and leave its type to be an int (>= 0) for future flexibility. Could've done with a string/enum to make it more defined and strict, but given it is an adv setting and current usage is so scarce thus leaving it flexible until further requirements arise.For
csv2
reader, ifparser_settings.debug
is 0 or omitted, which is the vast vast majority of existing and futurecsv2
schemas, no behavior changes; ifparser_settings.debug
isn't 0, then a__debug
node will be added to the record IDR structure, underneath which, currently onlyline_num
debug info will be added.This design is flexible for all future adoptions in all other file format readers, yet has zero impact on any existing schemas.
issue #227