-
Notifications
You must be signed in to change notification settings - Fork 36
OkHttp 3 #12
Comments
Indeed but we just use the automatically created client from swagger. Maybe they released a new version with a more recent okhttp or there is already an issue? |
I had a look into swagger code gen and they have different library versions available for java:
If we would choose retrofit2, we would get OkHttp3, but we would also get a different Gson version (not sure if this matters). I just tried that here. I haven't tested it though, just ran the generation and as usual swagger generates a huge change :). @devemux86, do you think your issue would be resolved with this update? BTW: I used Swagger-Codegen 2.2.3, which is still the current stable and it could not find the language R, maybe the current state of this repo was generated with a different version of the swagger codegen? |
Yeah, it was included recently and had to use master. |
If understand correctly the generated code, it uses OkHttp 3 and introduces new dependency for Retrofit? |
Yes :). Probably also not a good solution for Android? |
At least would have same OkHttp 3 version. 🙂 |
The simplest would be to create a PR at swagger codegen, they usually merge fast and this does not sound like a big change. Or at least create an issue there ;) |
Since client-hc uses OkHttp 3, is there a reason why directions-api-clients/java is still with OkHttp 2?
It's a bit inconvenient (specially on Android) to include double similar http libs, if want to use both clients together.
The text was updated successfully, but these errors were encountered: