Use Object.hasOwnProperty instead of prototype method #1233
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.
This PR addresses a situation uncovered with #1232 where the encode method calls
hasOwnProperty
of an object which may not have a prototype. This situation came about when mapping an express request to a grpc call, where aoneOf
object is a sub-message of a parent object. UsingObject.hasOwnProperty.call
appears to a safer approach which doesn't make assumptions about the underlying object's inheritance.