swagger-parser
swagger-parser copied to clipboard
swagger-api
Swagger Spec to Java POJOs
```json "/REST_Resource_3": { "put": { "consumes": [ "application/x-www-form-urlencoded" ], "produces": [ "application/json", "text/html" ], "parameters": [ { "name": "parameter123", "in": "query", "type": "array", "items": { "type": "string" }, "minItems": 2...
I have 2 components: 1. `ErrorArrayResponse` with property `errors` which is an array of `ApiResponseError` 2. `ApiResponseError` with 2 string properties, `errorType` and `message`. The problem is that after parsing,...
### Impacted swagger-parser versions: - 2.1.2 using `setInferSchemaType(false)` - 2.1.1 using `setDefaultSchemaTypeObject(false)` - 2.1.0 using `setDefaultSchemaTypeObject(false)` These result error messages (errors) are reported when parsing the below spec I have...
Here's a unit test that slowly goes nowhere with swagger-parser-v3 2.1.20, ignoring `maxYamlCodePoints` : ```java @Test public void testMaxCodePointsOpenApi31() { System.setProperty("maxYamlCodePoints", "999999999"); ParseOptions options = new ParseOptions(); options.setResolve(true); OpenAPIV3Parser parser...
This is a valid API key definition. ```yaml components: securitySchemes: ApiKeyAuth: # arbitrary name for the security scheme type: apiKey in: header # can be "header", "query" or "cookie" name:...
setResolve(true) tells OpenAPIV3Parser to load specs from external locations and put them in the model. ```Java ParseOptions parseOptions = new ParseOptions(); parseOptions.setResolve(true); OpenAPI openApiModel = new OpenAPIV3Parser().read(inputFile, null, parseOptions); ```...
When external referenced components have the same name but different definitions, only the first is considered, the rest seem to be ignored. This seems to be because of the way...
I used following code snippet to parse the OpenAPI definition and prettyprint it to a json value. But it seems like that the license.identifier is dropped out from the resulting...
Hello all, I don't know if this may be of interest, but I think I saw some issues logged here and there of people asking for this kind of behaviour....
Delegate resolving of relative URLs to Java framework, instead of solving that in custom code. Fix swagger-api/swagger-parser#750 ## Repro ```Java String rootPath = "https://raw.githubusercontent.com/Azure/azure-rest-api-specs/master/specification/storage/resource-manager/Microsoft.Storage/stable/2018-02-01/storage.json"; String relativePath = "../../../../../common-types/resource-management/v1/types.json"; String expected="https://raw.githubusercontent.com/Azure/azure-rest-api-specs/master/specification/common-types/resource-management/v1/types.json";...
