Default content-type for generated PUT request

[pabuisson]

Hi guys,

I'm using grape-swagger-rails (0.3.0) to generate the documentation for a JSON API. I have an issue with all the actions expecting a payload in JSON format : indeed, the documentation generates a request body with the application/x-www-form-urlencoded format, and my API only handles application/json format.

Therefore, all the "Try it out" actions on the documentation for POST/PUT/PATCH requests are non-functional.

I've tried to manually add a Content-Type header in the GrapeSwaggerRails initialization section, but it doesn't seem to be taken into account :

GrapeSwaggerRails.options.headers[ 'Content-Type' ] = 'application/json'

Am I missing something in the configuration of my endpoints / of grape-swagger-rails here ? I've found nothing around here in the documentation.

EDIT: actually it looks like the payload is correctly understood by my API endpoint on POST and PATCH, but not on PUT requests... in case it helps. Any clues ? When I click "Try it out", I get this in the console for a PUT request only :

[anelson425]

I am also seeing the same issue as documented here. @pabuisson did you ever find a solution for this?

[pabuisson]

@anelson425 well to be honest, we've kind of reduced our usage of grape-swagger so it's not that big a deal for us anymore. And re-reading this issue, I'm thinking that it must be coming from the underlying swagger-ui rather than grape-swagger-rails itself which mostly seems to be a wrapper around swagger. I found several issues in swagger-ui github issues, maybe there's more stuff over there about this problem.

[anelson425]

@pabuisson I found out yesterday that setting the param_type to 'body' in the documentation for the parameter seemed to fix my issue.

requires :body, documentation: { type: Entities::MyEntity, is_array: true, param_type: 'body' }

[h4ckbarth]

@anelson425, thank you so much, i was making a doc for my API and wasn't able to find a workaround for this. This fixed my issue!