fix(datastore): Handle loading nil values #8544
Merged
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.
Issue: In Go, any datatype is an alias for empty interface.
Getting entities with nil values in empty interface causes panic.
For sample code, please see: #8325 (comment)
Cause: When a reflect value is untyped nil, its type cannot be determined by using Type(). The code panics with error:
call of reflect.Value.Type on zero Value
Fix: If the field being set is an interface and the value to set is untyped nil, set the field to zero value.