-
-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Roslyn nullable annotations #537
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
# Conflicts: # src/Parquet/Parquet.csproj
Sorry, will have to revert this as it changes default behavior. My bad, I missed it during PR review. |
I could look at revising this pr to disable nullable support by default but any chances to consider changing the default in version 5? Working with files that are not generated by parquet.net is not intuitive without nullable support. There might be a compromise to limit issues and load null values into non nullable fields and simply show a warning. |
This is a fix for bug #535. The current parquet.net doesn't leverage compiler nullable when checking if members are nullable. This affects all classes - so any
string
property was marked as nullable in the schema. This PR adds checks for Roslyn's annotations to ensure that a field is nullable.