fix: validator.isValid is not a function
for certain objects
#946
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.
Description
Objects with keys like
valueOf
,toString
, and__proto__
cause aTypeError
to be raised when callingjwt.sign
. This is because the key technically does exist on theschema
param ofvalidate
, when checked withif (schema[key]) {}
. UsingObject.prototype.hasOwnProperty
solves the issue.I used
Object.prototype.hasOwnProperty.call(schema, key)
. This method has full browser support. Alternatively,lodash.has
could be installed and used, but I think that would be overkill.References
Fixes #945
Testing
I have added
test/issue_945.tests.js
. It fails if the change made tosign.js
is not present.Checklist