Petstore-Example: minimum/maximum definitions inconsistent

[nknapp]

Hi,

I don't know which project contains the example from http://petstore.swagger.io/v2/swagger.json, but I've found some inconsistencies that might need to be corrected:

• In DELETE /store/order/{orderId} the orderId-parameter has a minimum value set to 1.0, but the type is string. Is this possible in Swagger 2.0? The JSON-Schema-Spec says that minimum needs to be a number, so I would say, that type also needs to be a numeric type (i.e. integer, long, double or float)
• In GET /store/order/{orderId} the orderId-parameter is of type integer (int64), the description text says "For valid response try integer IDs with value <= 5 or > 10. Other values will generated exceptions", but the definition says { minimum: 1.0, maximum: 5.0 }. Is it even possible to define what the description says?

[webron]

Yeah, those are indeed issues. FWIW, it doesn't make the definition invalid but rather irrelevant.

The sample itself is found at https://github.com/swagger-api/swagger-samples/tree/master/java/java-jersey-jaxrs - if you'd like to submit a PR to resolve those issues, that would be great!

[nknapp]

I won't submit a pull request at the moment. If it would just be about changing a swagger-definition, that would be ok (2 clicks and some editing in the github editor). But cloning a java-project, making the changes and test if the sample is still working. That's too much effort for me at the moment, just to make an example nice.