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
{
"swagger": "2.0",
"info": {
"description": "This is a sample server Petstore server. You can find out more about Swagger at <a href=\"http://swagger.io\">http://swagger.io</a> or on irc.freenode.net, #swagger. For this sample, you can use the api key \"special-key\" to test the authorization filters",
"version": "1.0.0",
"title": "Swagger Petstore",
"termsOfService": "http://swagger.io/terms/",
"contact": {
"email": "[email protected]"
}
},
"paths": {
"/pet": {
"get": {
"parameters": [],
"responses": {
"default": {
"description": "successful operation",
"schema": {
"type": "array",
"items": {
"$ref": "#/definitions/ResponseModel"
}
}
}
}
}
}
},
"definitions": {
"Foo": {
"type": "object"
}
}
}
Will cause a NPE in the SpecFilter because there's no value to resolve to.
The text was updated successfully, but these errors were encountered:
surajchhetry
added a commit
to surajchhetry/swagger-core
that referenced
this issue
Sep 15, 2016
A definition like such:
Will cause a NPE in the SpecFilter because there's no value to resolve to.
The text was updated successfully, but these errors were encountered: