Post by tophercantrell on Jul 7, 2017 21:18:48 GMT
JSON does not different numeric types like "integer" and "float". Everything is just a "number", which can be integers or floats.
Some values in the schema like "PowerConsumedWatts" are definitely floats. Some values in the schema like "MaxPasswordLength" are definitely integers.
The schema definition defines both values as simply "number". Is there an easy way (other than with context) for clients to know how to restrict user inputs to pure integers where appropriate?
Some values in the schema like "PowerConsumedWatts" are definitely floats. Some values in the schema like "MaxPasswordLength" are definitely integers.
The schema definition defines both values as simply "number". Is there an easy way (other than with context) for clients to know how to restrict user inputs to pure integers where appropriate?
