Comments (3)
The correct check for "integer"
types is definitely is_int($value)
without the ctype_digit($value)
which returns true for strings (e.g. "12"
). Strings are not valid integers according to the latest draft v4.
The "number"
type also has the same problem as "integer"
. The code uses is_numeric($value)
which returns true for strings (e.g. "12.5"
). So a better check would simple reject strings altogether.
Also notable is that there are two constants declared in Constraints/Constraint.php.
const CHECK_MODE_NORMAL = 1;
const CHECK_MODE_TYPE_CAST = 2;
I searched throughout the code and found that these constants are never anywhere used except in one of the unit test files, PhpTypeCastModeTest.php
. These tests are in fact erroneous.
Schema validation doesn't support casting so you can never pass a string for "integer"
, "number"
, or "boolean"
types. Draft v3 and v4 compliant validation should reject strings for these types altogether.
I believe that the above constants can be removed from the code entirely and the unit test file deleted. Any new type tests can be added to existing unit test files, such as NumberAndIntegerTypesTest.php
.
from json-schema.
This issue has been fixed by merging #41 into master.
from json-schema.
Thanks for adding the fix for this @mchiocca.
from json-schema.
Related Issues (20)
- Show line numbers HOT 4
- Schema validation always returns true HOT 2
- Validation always returning true HOT 4
- oneOf, and anyOf annotation example HOT 4
- URI schemas incorrectly validated with FILTER_VALIDATE_URL HOT 7
- JsonSchema\Exception\InvalidArgumentException HOT 2
- JsonSchema\Exception\InvalidArgumentException | is an invalid type for string|null HOT 5
- HTTP to HTTPS redirection breaks remote reference resolution HOT 3
- not validating nested array with Symfony phpunit, or prop names HOT 3
- Possibly enum check is O(n) maybe can be O(1) for more performance HOT 4
- Why do we support higher version json-schema? HOT 3
- Inconsistent behavior with allOf/oneOf between master branch and latest release (v5.2.13) HOT 6
- Version number format changed in 5.2.13 HOT 2
- Mixing properties and patternProperties fails for properties not matching the patternProperties definition HOT 4
- Latest version named `v5.2.13` introduced issues in other soft that use versionning comparaison HOT 7
- bug: anyOf / oneOf with objects and default values HOT 5
- bug: type order in 'allOf' has an impact HOT 3
- Fatal error: Uncaught Error: Class 'Opis\Uri\Uri' not found HOT 2
- Triage on Issues & Pull requests HOT 1
- Type coercion not working properly in 5.2.13 HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from json-schema.