This repository has been archived by the owner on Mar 26, 2024. It is now read-only.
more persistent flag storage #39
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wheresrhys
force-pushed
the
rhys/flag-persistence
branch
3 times, most recently
from
7bd9190 to
8bca356
Compare
wheresrhys
added a commit
that referenced
this pull request
Aug 5, 2016
…-worker into rhys/flag-persistence * 'master' of https://github.com/Financial-Times/n-service-worker: more persistent flag storage (#39)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
because service workers shut themselves down, losing global scope, and the spec is probably going to change to allow browsers to spin up multiple sw instances, getting this out to make sure flags behave
@ironsidevsquincy