-
Notifications
You must be signed in to change notification settings - Fork 103
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
Fix for parsing "null" values for auto-value objects. #23
Conversation
* updated auto-value version.
Thanks for the PR. It looks like this caused the tests to fail, and also needs tests for your addition. |
@rharter no problem. I didn't updated tests for this. But I've tested it manually and it's working like a charm :-) |
@radzio Are you planning to add tests for your changes? I won't be merging in untested code. |
Hello @radzio, Are you planning to add tests for this fix? I'm interested in merging this PR. If you don't have time I can step in to write the tests. |
@R4md4c Are you still up for writing tests for this and rebasing it? |
@rharter Yes, I'm still up for it, but I'm wondering whether I should open a new pull request or I use the current pull request? |
You can always check out his branch into your own fork and make a new PR. |
@rharter I use |
I tried to write a test for this PR before applying the patch (after rebasing with upstream) to check what problem it does solve, but I realized that it doesn't solve anything when trying to read a null auto value object from the JSON string as it reads it without a problem. Perhaps I misunderstood what problem this PR solves? Here is the test method
Here is what I added to the
|
This closes rharter#23, rharter#50 and rharter#67
This closes rharter#23, rharter#50 and rharter#67
This closes rharter#23, rharter#50 and rharter#67
No description provided.