Generate correct "type" for Integer fields #118
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.
Closes #117
Using a
type
ofnumber
and aformat
ofinteger
is not documented in the JSON schema specification as a correct way to represent integers. Instead, atype
ofinteger
should be used as this ensure that validators will correctly validate inputs as an integer and not acceptnumber
values.This is a breaking change as there is potential for previous successful validations to fail if users are validating
number
(e.g. floats) values against integer fields.