-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code generated for APIs requiring text/plain (etc.) as request content type not useful #109
Comments
Only Application/JSON and Multipart/form-Data are implemented |
Are you happy for me to contribute a fix? |
This is still something I believe swagger codegen would benefit from, and I was happy to contribute an implementation, but I'd hoped for confirmation that you thought my proposal made sense... |
so, what your mean? and codegen result like ?do you provide an example? |
Completed untested, but perhaps something like
|
look forward to you submit full example |
@wizofaus There is a new release which should solve your issue with plain text: https://github.com/Manweill/swagger-axios-codegen/releases/tag/v0.16.0 Please feel free to test it and close this issue if you are happy. |
Don't really see how it generates a client-stub that will actually support uploading the plain-text content, but I haven't tried TBH. Do plan to start using this tool again soon actually so will let you know. |
We have a couple of APIs for uploading documents, that in our swagger look like, e.g.:
But the function generated by swagger-axios-codegen has
i.e., there's no way to pass in the actual contents to upload to the API!
Again, I could look at contributing a fix, but is this something you'd come across before?
We also have some APIs that require application/octet-stream as the input (binary file uploads).
Thanks!
Dylan
The text was updated successfully, but these errors were encountered: