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
Yes, you are right. I forget that this doclet still creates a swagger 1.2 compliant api declaration and that the "id" field of model object has been removed from swagger 2.0. I know that you guys were going to roll out a swagger 2.0 compliant doclet some time ... did you guys put that on the back burner for a bit?
@gautampriya i'm the only major committer at present and can only work on it every so often in my spare time so am currently only able to work on reported bugs, i hope to have more time to work on a 2.0 version at some stage but thats going to be a chunky feature so realistically will be a fair while
"models" : {
"ErrorMessage" : {
"id" : "ErrorMessage"
"properties" : {
"message" : {
"type" : "string",
"description" : "Description of the error condition"
},
"status" : {
"type" : "string",
"description" : "Contains redundantly the HTTP status of the response sent back to the client in case of\n error, so one does not have to look into the response headers.",
"enum" : [ "OK", "CREATED", "ACCEPTED", "NO_CONTENT", "RESET_CONTENT", "PARTIAL_CONTENT", "MOVED_PERMANENTLY", "FOUND", "SEE_OTHER", "NOT_MODIFIED", "USE_PROXY", "TEMPORARY_REDIRECT", "BAD_REQUEST", "UNAUTHORIZED", "PAYMENT_REQUIRED", "FORBIDDEN", "NOT_FOUND", "METHOD_NOT_ALLOWED", "NOT_ACCEPTABLE", "PROXY_AUTHENTICATION_REQUIRED", "REQUEST_TIMEOUT", "CONFLICT", "GONE", "LENGTH_REQUIRED", "PRECONDITION_FAILED", "REQUEST_ENTITY_TOO_LARGE", "REQUEST_URI_TOO_LONG", "UNSUPPORTED_MEDIA_TYPE", "REQUESTED_RANGE_NOT_SATISFIABLE", "EXPECTATION_FAILED", "INTERNAL_SERVER_ERROR", "NOT_IMPLEMENTED", "BAD_GATEWAY", "SERVICE_UNAVAILABLE", "GATEWAY_TIMEOUT", "HTTP_VERSION_NOT_SUPPORTED" ]
}
}
}
}
The text was updated successfully, but these errors were encountered: