feat(retrofit2): Improvise OkHttpClientProvider to accept interceptors #1220
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As an alternate to using
OkHttp3ClientConfiguration
for creating an OkHttpClient,OkHttpClientProvider
was created through#639. But there are many existing retrofit clients that are passing Interceptor(s) which is not supported by
OkHttpClientProvider
. This PR allowsOkHttpClientProvider
to acceptokhttp3.Interceptor
list.As we are slowly moving to retrofit2(rosco completed, echo under review), the real consumer of OkHttpClientProvider will be
Retrofit2ServiceFactory
(as opposed toRetrofitServiceFactory
) but since it's an implementation ofServiceClientFactory
, I had to add a method that takesList<Interceptor>
which is specific toRetrofit2ServiceFactory
and hence the method has no significance wrtRetrofitServiceFactory
.The idea is to use
OkHttpClientProvider
instead ofOkHttp3ClientConfiguration
while upgrading the http clients from retrofit1 to retrofit2.