feat: add pwa.cache.*
option to precisely control caching
#1501
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.
Type of change
Description
Expanded several options for setting the pwa cache in the configuration file
_config.yml
:Added option
pwa.cache.deny_paths
to remove unnecessary cached content from PWA.When a user has one or more sub-sites (delimited by baseurl) under a domain, then the PWA needs to recognize the URL of the external site to avoid caching invalid resources.
Specific scenarios discussed in detail in #1424.
Support to delete PWA cache on user's browser. (Set
pwa.cache.enabled
tofalse
)Website can remove PWA features, including installation. (Set
pwa.enabled
tofalse
)app.js
/sw.js
is hard to maintain when mixed with liquid, so refactor to pure JS and manage byrollup
.Additional context