Jake Wharton
Jake Wharton
It's only recommended, not required. Regular protobuf works fine as well.
What is the final URL of that example and how is it different than regular query parameters? On Sat, Aug 3, 2019, 2:01 AM Alex wrote: > In Stripe APIs...
I don't really understand how this is useful over `@Query`-annotated parameters. Can you please provide an example of what you are trying to achieve that is impossible with `@Query` and...
There is a test case that proves `encoded=true` works: https://github.com/square/retrofit/blob/90729eb2ae2f3329281c1f9813ab1de3daa71ad0/retrofit/src/test/java/retrofit2/RequestBuilderTest.java#L1488-L1498. What output do you get when you use it?
Stop spamming our issues. This is your one and only warning. (Their comment was since deleted) On Fri, Jun 3, 2016 at 12:41 AM AMIT SHEKHAR [email protected] wrote: > You...
Retrofit currently buffers all request data, yes. We don't have a good workaround here, especially not for a composite request such a multipart.
This is not supported. The only way would be to build a `MultipartBody` yourself and pass it to a service method that accepted a `RequestBody`. What's your use case?
To be clear, the API you're talking to _requires_ that you use that boundary?
Yeah I think in the next major version I'll abandon the unified `Converter` interface and create separate ones so that additional information can be provided. There's a bunch of design...
I can't think of a good workaround for now either. The only way to sneak data into the converter would be to put it inside the content type. So you...