Support configuring ApolloClient
with lazily initialized Call.Factory
.
#5784
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.
Resolves #5775
I've tested this locally:
Eager
OkHttpClient
init:Lazy
OkHttpClient
init:Creation of
ApolloClient
no longer crates anOkHttpClient
.The creation ofOkHttpClient
is now deferred to after the "App Startup" window (by CoilImageLoader
).Correction: the
OkHttpClient
is still created within the "App Startup" window, but it's done in a background thread by Coil.The actual perf impact of using the lazy API obviously depends on each app.