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
While working on #90 I was having troubles on writing a simple test that sends a file to the mock server.
This was mostly caused by the fact that the mock server is receiving the toString representation of the RequestBody and not its real content.
At this point I'm not 100% sure that the current plugin is able to generate proper retrofit APIs that allow file uploads.
The scope of this issue is to track the effort needed, if any, to ensure file upload capabilities.
The text was updated successfully, but these errors were encountered:
I do have some conclusive results over here.
I'm currently preparing a PR to address the issue and to write the missing tests of #90 .
According to the swagger specifications in order to send files the operation must consume multipart/form-data (doc). The junit-tests file endpoint does not define multipart/form-data and so the generate code does not work well.
Considering this we have two alternatives:
Find a way to make it work anyway
Stick to the swagger specifications and annotate the endpoint as unsafe so we will discourage usage of the endpoint.
While working on #90 I was having troubles on writing a simple test that sends a file to the mock server.
This was mostly caused by the fact that the mock server is receiving the
toString
representation of theRequestBody
and not its real content.At this point I'm not 100% sure that the current plugin is able to generate proper retrofit APIs that allow file uploads.
The scope of this issue is to track the effort needed, if any, to ensure file upload capabilities.
The text was updated successfully, but these errors were encountered: