[Data Types] Fix minimum and maximum types

[webron]

Right now, the type for minimum and maximum fields is string. Besides the fact that this can lead to funny errors, we want to make sure we follow the JSON Schema definitions and convert the type to number.

[vincentjames501]

+1. Also, is there any reason why minimum and maximum don't apply to type string as well? Seems only logical that one would want to validate the length of a string.

[mission-liao]

I'm not sure if it's the same issue, if it's not ok to append this to the issue, please let me know.

Now I found that the string representation of minimum & maximum is always number, even if their type is integer. Ex. in http://petstore.swagger.wordnik.com/api/api-docs/pet, we can find this:

{
"name":"petId",
"description":"ID of pet that needs to be fetched",
"required":true,
"type":"integer",
"format":"int64",
"paramType":"path",
"allowMultiple":false,
"minimum":"1.0",
"maximum":"100000.0"}

Is it expected?

[webron]

@vincentjames501 - in Swagger 2.0 the validation fields would be the same as they are in json schema draft 4. If minimum and maximum apply to string in the schema, they would be applied here as well.

@mission-liao - it's pretty much the same issue, yeah. As mentioned above, it'll be changed in Swagger 2.0.

[webron]

@vincentjames501 - FYI, for string the proper attributes are minLength and maxLength, both of which are introduced in Swagger 2.0.

[webron]

This has been resolved in Swagger 2.0.