swagger-parser
swagger-parser copied to clipboard
swagger-api
Swagger Spec to Java POJOs
In Dealing with Let's Encrypt, "may not be sufficient on it's own", remove the apostrophe so it is instead "may not be sufficient on its own".
I am using swagger-parser 2.1.25 and when I parse an OpenAPI document [openapi-properties-additionalProperties.json](https://github.com/user-attachments/files/18535026/openapi-properties-additionalProperties.json) using these ParseOptions: ``` ParseOptions parseOptions = new ParseOptions(); parseOptions.setResolve(true); parseOptions.setResolveRequestBody(true); parseOptions.setResolveFully(true); OpenAPI openAPI = new OpenAPIV3Parser().read("src/main/resources/openapi-properties-additionalProperties.json",...
**Description:** When I parse an OpenAPI 3.0 document using new OpenAPIV3Parser().readContents(...), a default server with URL "/" is automatically added if no servers are defined. This causes issues when the...
related issue: https://github.com/swagger-api/swagger-parser/issues/1981 After including swagger-parser (implementation("io.swagger.parser.v3:swagger-parser:2.1.25") ) as dependency i have runtime exception when open swagger page: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlElement To remove this error i shoude exclude: exclude(group: 'io.swagger.core.v3') Full...
OpenAPIV3Parser does not seem to work as one would expect when openapi components have circular dependencies of any kind. _**Expected behaviour:**_ All `$ref`s are resolved. If the schema references itself...
We have a Kotlin interface which gets implemented in multiple data classes: ``` @Schema( type = "object", oneOf = [A::class, B::class, C::class], ) interface I { val userMessage: String val...
There is a simple example: I have specification: _openapi_test.yaml:_ ``` openapi: 3.0.3 info: title: test description: test version: 1.0.0 servers: - url: '/' tags: - name: test1 description: "test" paths:...
In attempted to use swagger-codegen to read a 3.1.0 schema vs a 3.0.x schema, a notable change has occurred in how arrays are handled. For example when provided the following...
In the parsing of schema (`io.swagger.v3.parser.util.OpenAPIDeserializer::getSchema`), it is just processed the `$ref` field and return the schema Object and without processing the extension part. [Code](https://github.com/swagger-api/swagger-parser/blob/639e9e3b56b39670d59c21c7888b8f5b2c15a0b5/modules/swagger-parser-v3/src/main/java/io/swagger/v3/parser/util/OpenAPIDeserializer.java#L2796)
We encountered the issue here, when using OpenAPITools Generator (Maven Plugin) after we switched from OAS 3.0.3 to 3.1.0: https://github.com/OpenAPITools/openapi-generator/issues/18161 As the Issue on OpenAPITools indicates, the error might be...
