Check field nullability for custom extension types #69
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.
For custom extension types (currently automatically supported for
Char
and
Symbol
types), we were failing to take into account whether thefield was nullable or not; this led to the case where a column might be
['a', missing]
, but when deserializing, the column type was justChar
instead ofUnion{Char, Missing}
. The fix is to enhance theArrowTypes.extensiontype
function to also take thefield
argumentand check the nullability before returning.
Fixes #68