Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support object equivalents of primitives #1

Closed
wants to merge 1 commit into from

Conversation

kenany
Copy link

@kenany kenany commented Aug 1, 2014

This patch fixes the type checks for strings, numbers, and booleans so that the object equivalents of these primitives are recognized. Without this patch, values like new String('world'), new Number(0), and new Boolean(false), were not being recognized as strings, numbers, and booleans.

@kenany kenany changed the title Support primitives Support object equivalents of primitives Aug 1, 2014
kenany added a commit to kenany/is-my-json-valid that referenced this pull request Aug 1, 2014
This patch fixes the type checks for strings, numbers, and booleans so that
the object equivalents of these primitives are recognized. Without this patch,
values like `new String('world')`, `new Number(0)`, and `new Boolean(false)`,
were not being recognized as strings, numbers, and booleans.

Closes mafintosh#1
kenany added a commit to kenany/is-my-json-valid that referenced this pull request Nov 4, 2014
This patch fixes the type checks for strings, numbers, and booleans so that
the object equivalents of these primitives are recognized. Without this patch,
values like `new String('world')`, `new Number(0)`, and `new Boolean(false)`,
were not being recognized as strings, numbers, and booleans.

Closes mafintosh#1
kenany added a commit to kenany/is-my-json-valid that referenced this pull request Jan 29, 2015
This patch fixes the type checks for strings, numbers, and booleans so that
the object equivalents of these primitives are recognized. Without this patch,
values like `new String('world')`, `new Number(0)`, and `new Boolean(false)`,
were not being recognized as strings, numbers, and booleans.

Closes mafintosh#1
This patch fixes the type checks for strings, numbers, and booleans so that
the object equivalents of these primitives are recognized. Without this patch,
values like `new String('world')`, `new Number(0)`, and `new Boolean(false)`,
were not being recognized as strings, numbers, and booleans.
@kenany kenany closed this Feb 11, 2015
LinusU pushed a commit that referenced this pull request Dec 18, 2017
default schemaPath in visit anyOf or oneOf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant