Not sure why it’s not, but position should be deprecated from that annotation. It’s definitely not supported by the spec.
From: <[email protected]> on behalf of Chris Cosentino <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Friday, August 11, 2017 at 14:40 To: Swagger <[email protected]> Subject: ApiModelProperty annotation - "position" element not supported in 2.0 Schema? Hello! We are using Swagger Annotations and for the APIModelProperty annotation (http://docs.swagger.io/swagger-core/current/apidocs/io/swagger/annotations/ApiModelProperty.html) we use the position element. However, when trying to validate against the swagger 2.0 specification (https://raw.githubusercontent.com/OAI/OpenAPI-Specification/master/schemas/v2.0/schema.json) it returns an error: jsonschema.exceptions.ValidationError: u'position' does not match any of the regexes: u'^x-' Is the annotation API incorrect in stating that it supports the position element, or is the swagger schema missing the position element? I understand we can get around this by prefacing the name of the "position" property with "x-", but we were trying to follow the standards. The reason we use the position property is to order the properties for any given API model manually for better readability. Is this an omission in the 2.0 schema? Thanks much, Chris -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
