Hash website build so service worker can detect changes #1526
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.
Motivation for the change, related issues
We need some way to detect whether the app has been updated since we last cached app resources. This may not be the way, but it can kick off discussion. This PR starts by adding the website hash to a standalone file, but to avoid a network request, we may prefer to embed it in a file like the service worker script. cc @bgrgicak @adamziel
Related to #133
Implementation details
We need to decide where to put the hash.
The hash itself is derived from a list of hashes of all website files sorted by path.
Testing Instructions (or ideally a Blueprint)
TBD