OriginalRef is added with $Ref swagger v2.0 (version used 2.9.2)
See original GitHub issueI am using springfox-swagger2-2.9.2 but when swagger document is generated its adding originalRef in the response which throws error additional property originalRef not allowed.
parameters: - in: "body" name: "passwordChange" description: "passwordChange" required: true schema: "originalRef": "PasswordChangeReq" $ref: "#/definitions/PasswordChangeReq" responses: 204: description: "Password successfully updated" 400: description: "Bad Request" schema: originalRef: "ResponseError" $ref: "#/definitions/ResponseError"
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:10 (2 by maintainers)
Top Results From Across the Web
OpenAPI Specification - Version 2.0 - Swagger
Version 2.0 specification defines a set of files required to describe an API. These files can then be used by the Swagger-UI project...
Read more >Replace @EnableSwagger2 after update to latest version
I migrated to latest springfox-swagger2 version 2.10.0 but looks like @EnableSwagger2 is deprecated. What annotation should I use in order to ...
Read more >Springfox Reference Documentation - GitHub Pages
With Swagger 2.0 things are much simpler and an application's API can be represented in a single JSON file. 5.2. Moving from swagger-springmvc?...
Read more >atlassian / swagger-request-validator / issues / #194 - Bitbucket
Which version of these libraries shall i use for swagger v 2.0? ... property originalRef , which is not allowed by the Swagger...
Read more >Setting Up Swagger 2 with a Spring REST API - Baeldung
At the same time, the API documentation should be informative, readable, and easy to follow. Moreover, reference documentation should ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The issue still exists.
You just have to add it as bean to the spring context.