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.

Sign up for GitHub

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

Jump to bottom

when schema type is integer but max/min value is a float point number #160

Closed
BalloonWen opened this issue Jun 5, 2019 · 1 comment
Closed

when schema type is integer but max/min value is a float point number #160

BalloonWen opened this issue Jun 5, 2019 · 1 comment
Assignees
@BalloonWen
Labels
bug

Comments

@BalloonWen
Copy link
Contributor

whenever there's a combination like:
{"type": "integer",
"maximum": 1e+32}
will validate error
@BalloonWen BalloonWen added the bug label Jun 5, 2019
@BalloonWen BalloonWen self-assigned this Jun 5, 2019
BalloonWen added a commit that referenced this issue Jun 11, 2019
@BalloonWen
Merge branch 'master' of github.com:networknt/json-schema-validator i…
ef1c6da 
…nto fix/#160-max-value-float
@BalloonWen BalloonWen mentioned this issue Jun 11, 2019
Merged
stevehu added a commit that referenced this issue Jun 14, 2019
@stevehu
Merge pull request #164 from networknt/fix/#160-max-value-float
17e90d8 
Fix/#160 max value float
@stevehu
Copy link
Contributor

stevehu commented Jun 14, 2019

when schema type is integer but max/min value is a float point number

@stevehu stevehu closed this as completed Jun 25, 2019
@BalloonWen BalloonWen mentioned this issue Jun 25, 2019
Closed
@kosty kosty mentioned this issue Jul 16, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BalloonWen BalloonWen

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stevehu @BalloonWen