If localStorage is not available, use a in-memory none expiring assig… #71
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.
…nment cache (FF-2110)
labels: mergeable
Fixes: #issue
Motivation and Context
When
init
is called, alocalStorage
assignment cache is created. However if nolocalStorage
is available it always returns non-cachable return values, effectively being no cache. This is going to happen on chrome extensions and other environments without alocalStorage
.Description
localStorage
is available, create an in-memory assignment cache. This is an improvement over the current behavior as at least there will be some caching happening, even though it is reset each session.environment.ts
How has this been tested?