feature: record unparsed lines instead of skipping them #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
davidjrice
force-pushed
the
djr/unparsed
branch
from
b8c5097 to
96bcfdb
Compare
This was referenced Apr 11, 2024
…g the record_identifier before parse * negates the need for looping over methods, improving performance * allows tracking of unparsed lines and returns then in the result hash as :unparsed
davidjrice
force-pushed
the
djr/unparsed
branch
from
4676edf to
249c553
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
record identifierbefore attempting to call aparsemethod on a given lineUnidentifiedRecordErrorif an unidentified record is foundunparsedlines and returns them in the resultant data hash asresult[:unparsed]