feat(analytics-remote-config): remove idb #855
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
This is removing the use of IDB from remote config in favor of relying on browser caching to help support remote config fetching. There were definitely options to use IDB in other ways, but currently it's a bit broken when trying to support multiple namespaces. Rather than trying fix it, we'll see if just relying on the cache-control header and the browser cache to solve the problem.
kwalker3690
approved these changes
Aug 23, 2024
|
Nope! It's already in place. |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This is removing the use of IDB from remote config in favor of relying on browser caching to help support remote config fetching. There were definitely options to use IDB in other ways, but currently it's a bit broken when trying to support multiple namespaces. Rather than trying fix it, we'll see if just relying on the cache-control header and the browser cache to solve the problem.
Checklist