You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @trufanov-nok, hopefully this answer reaches you at a time that it is still relevant.
To the best of my understanding, JSON Schema doesn't place any hard constraints on the range supported by the integer type. Therefore the actual range is going to depend on the JSON Parser being used, and maybe even the OS/compiler (e.g. 32-bit vs 64-bit).
To help explain this, here is the actual code that checks integer types (in validation_visitor.hpp):
case TypeConstraint::kInteger:
valid = m_target.isInteger() || (!m_strictTypes && m_target.maybeInteger());
break;
The call to m_target.isInteger() here is what determines whether a value is an integer. The isInteger() method is provided by the adapter, and for pretty much all adapter types, it just asks the underlying parser whether the value is an integer.
I has declared a type constraint:
And was surprise to find the following violates it:
"graphId": 3658777115
The value is > Int32 but < UInt32
The "type": "numeric" works fine.
Should it be so?
The text was updated successfully, but these errors were encountered: