feat(image): [android] adding cache control option #14
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.
Summary:
As follow up from ... and ...,
force-cacheis the last missing option to have caching control pair up with how it currently works for iOS.Local caching options remain the same, if there is cache available we return the cached image locally. Otherwise we proceed to the request.
For the image network request, we now use the
okhttp3.CacheControldirectiveFORCE_CACHEif we pass theforce-cacheoption from the JS side.Changelog:
[ANDROID] [ADDED] - Image
force-cachecaching control optionTest Plan:
New example added to the RNTester under the cache policy examples. Then inspecting that the cache control is set correctly before sending it in the
okhttp3.Requestbuilder.This case was a bit more tricky to test in terms of e2e as it would involve some caching in the server as well, I'm open to suggestions to make this more complete.