swagger-parser
swagger-parser copied to clipboard
swagger-api
Swagger Spec to Java POJOs
As describe in this issue https://github.com/OpenAPITools/openapi-generator/issues/18361 I have a difference in the parser behavior. With 3.0 schema, the reference to an external component is parse with it's own structure. It...
**Description:** The current swagger-parser (version 2.1.21) fails to parse the referenced ArraySchema in the provided Swagger YAML file. When attempting to resolve the schema, the parser returns a null value...
When the path level parameters are defined as refs we seem to run into this problem. In this case the relative file to be loaded is present inside the `path_level_params_spec/sub-dir`...
Given the following files: ```yaml openapi: 3.0.3 info: title: Sample API version: 1.0.0 paths: /users/: get: parameters: - $ref: 'headers.yml#/XRequestId' responses: '200': description: Ok headers: X-Request-Id: $ref: 'headers.yml#/XRequestId' ``` and...
When I use `swagger-parser` in combination with Spring Boot 3, and I run my unit tests from IntelliJ, they pass. However, when I run them using Gradle (which I assume...
[The Azure OpenAPI specification](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-03-01/virtualMachine.json#L3321) uses "properties" in definitions that also have `allOf` i.e. are a `ComposedModel`. I don't know if this is valid or not, but Swagger should support parsing...
``` openapi: 3.0.0 info: title: Example API version: 1.0.0 paths: /example/{id}: parameters: - $ref: '#/components/parameters/ExampleParam' get: responses: '200': description: Successful response content: application/json: schema: $ref: '#/components/schemas/ExampleSchema' /example2: post: requestBody: $ref:...
