When setting a default object to POST it removes option to send as application/json

[swagger-api]

When setting a default object to POST it removes option to send as application/json

[vemahendran]

I too face the same type of issue.

"{"apiVersion":"1.0.0","swaggerVersion":"1.2","basePath":"http://localhost:3000\",\"resourcePath\":\"/admin\",\"apis\":[{\"path\":\"/admin/user/{user}\",\"operations\":[{\"description\":\"Operations about user","method":"GET","summary":"Find userdetails by user name","notes":"Returns a user detail based on NAME","type":"User","nickname":"getUserDetailsByName","produces":["application/json"],"params":[{"name":"user","description":"NAME of user that needs to be fetched","type":"string","required":true,"paramType":"path"}],"responseMessages":[{"code":400,"message":"invalid name"},{"code":404,"message":"user not found"}]}]}],"models":{}}"

The response is directly sent to the express core response method. It will be good if swagger allows custom middleware (i.e. resides on user app) to manipulate the response, and the custom middleware can take care of routing to express response method.

Currently, I have removed JSON.stringify on the response data in my fork.
vemahendran@9bb062a

If you are good to allow middlewares for after routes, i can fix it, and send a PR.

[fehguy]

this is ancient, but still valid. Moved here:

swagger-api/swagger-ui#702