Updated for loops over Objects to check hasOwnProperty #396
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.
Discovered problem with how the eris handles
for ... in
loops forObject
once a customObject.prototype
has been defined. Solution was to verifyObject.hasOwnProperty()
.All
for
loops in the library were examined and, if needed, corrected. There were a couple of exceptions, which I did not modify, that usedObject.keys()
method to "automatically" correct this issue.Credit to Notice Me on Discord for figuring this one out.