-
Notifications
You must be signed in to change notification settings - Fork 94
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
Nullable values #100
Nullable values #100
Conversation
c776c12
to
4f06094
Compare
Codecov Report
@@ Coverage Diff @@
## master #100 +/- ##
==========================================
+ Coverage 92.41% 92.81% +0.40%
==========================================
Files 6 6
Lines 2439 2465 +26
==========================================
+ Hits 2254 2288 +34
+ Misses 185 177 -8
Continue to review full report at Codecov.
|
445b94e
to
cc8c71a
Compare
I came a cross this difference during testing of SAP#95 I decided to set tzinfo of JSON DateTimes to simplify my tests and it also make sense to me to have the values configured the same way.
Tests will appear in the next commit. I don't find it usefull to add the tests here.
Only a declared property knows if it accepts Null or not. I was playing with nullable Type but than I would have to have also nullable TypeTraits and there result would be a complete mess. Therefore I decided to move the responsibility to serialize/deserialize the declared property. The decision led to a simpler code which is a good sign. I could have used a better exception type but we currently evaluating the best exception strategies, so I used a generic type. Part of the issue SAP#95
cc8c71a
to
ce0b6cf
Compare
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.
Looks good to me, comments resolved.
No description provided.