fix: split(...).every is not a function #166
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.
Description
If you validate invalid data with a schema like
v8n().every.schema(...)
, you get a validation error which is actually triggered by a type error (split(...).every is not a function
). This results in a malformed validation error.The issue is fixed by type checking the value before splitting it. Not sure if this is the correct solution, because I don't really understand what's happening here at Rule.js#L29, the source of the issue.
Type of change
Checklist:
master
Unreleased
section of the CHANGELOG