feat: change the order of default runtimeCache #106
Merged
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.
Overview
By default, runtimeCache is added for base URL as below.
Then, I have an problem.
When I add runtimeCache for
/api/xxxxxx
and set the strategy except fornetworkFirst
, for examplecacheFirst
, it doesn't work because of the order.I want to change the default runtimeCache order to avoid this problem.
example setting
example output
I intend that the request for
/api/xxxxxx/.*
refers to cache firstly.But it fetches the data from network firstly.
Solution
/api/xxxxxx
matches with both url pattern. Then the first pattern is adopted on workbox.I think the default runtimeCache setting should be set to the last by default.
Current Work Around
I have an idea to avoid that situation but it is somewhat complex.
false
tooffline
optionruntimeCache
optionexample setting
example output
It works.