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
We are trying to migrate from spring fox to spring doc as the former is no longer compatible with the latest spring boot version ( 2.6.x) and spring doc internally used open API specification ( 3.0.1). So I thought this might be the correct forum to raise the issue.
We have made all the migration changes and everything is working perfectly in my local but when we try to deploy to one of our ec2 instances we are facing the below issue. The swagger validator badge is invalid.
And on clicking the Invalid Json symbol we are getting the below error message,
I have fetched my swagger JSON file ( from the v3/api-docs) and checked in swagger editor it is not having any parsing errors, it just has a couple of semantic errors ( delete method expecting a request body ) can anyone point me to the reason we are getting it or tell me how to get more details on the issue?
The text was updated successfully, but these errors were encountered:
Hi there,
We are trying to migrate from spring fox to spring doc as the former is no longer compatible with the latest spring boot version ( 2.6.x) and spring doc internally used open API specification ( 3.0.1). So I thought this might be the correct forum to raise the issue.
We have made all the migration changes and everything is working perfectly in my local but when we try to deploy to one of our ec2 instances we are facing the below issue. The swagger validator badge is invalid.
And on clicking the Invalid Json symbol we are getting the below error message,
I have fetched my swagger JSON file ( from the v3/api-docs) and checked in swagger editor it is not having any parsing errors, it just has a couple of semantic errors ( delete method expecting a request body ) can anyone point me to the reason we are getting it or tell me how to get more details on the issue?
The text was updated successfully, but these errors were encountered: