Don't break when values are null #20
Merged
Conversation
This file contains hidden or 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
running .toString on null throws an error. This mitigates the error. I'm unsure what the return type should be in case of a null value. null? an empty string? Please advise!
DvirDukhan
reviewed
Jun 16, 2019
There was a problem hiding this comment.
@davidLeonardi please add/modify unit tests with this change
DvirDukhan
added a commit
that referenced
this pull request
Aug 5, 2019
DvirDukhan
previously approved these changes
Aug 5, 2019
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.
Some values can be empty, which leaves them with a null value.
For example, 'n.notHere' will be null.
Now, running .toString on null throws an error.
This fix mitigates the error.
Yet I'm unsure what the return type should be in case of a null value. null? an empty string? Please advise!