Skip prototype properties when looping over objects in objToPaths() #74
Conversation
This file contains 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
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.
objToPaths() is looping over objects not skipping the ones in the
[[Prototype]]chain. Therefore, custom objects that have properties/methods in theprototypeare being looped over as well. This creates an issue in theset()method where not only properties belonging to the custom objects are taken to get the shallow ('keyed with path names') object but also all the methods defined on its prototype.Using
hasOwnProperty()check is the recommended way to skip the ones defined in the prototype.