fix: A sample column value of 0|0 is not being parsed correctly #178
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
JarvisVon
force-pushed
the
feature/fix-sample-value-parsing
branch
from
e271b94
to
7b9dc85
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.
The previous implementation was using
header.RESERVED_INFOSfor bothheader.get_info_field_infoandheader.get_format_field_info. This change updates the behavior so thatheader.get_format_field_infomakes use ofheader.RESERVED_FORMAT. Additionally, theFieldInfoobtained inheader.get_info_field_infoandheader.get_format_field_infofrom theheader.RESERVED_INFOS/header.RESERVED_FORMATdicts are returned as is, without creating a newFieldInfoobject.Closes #176