Firebase Remote Config #120
Open
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
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.
This PR adds support for Firebase RemoteConfig through multiple components:
RemoteConfig: This component instantiates a firebase RemoteConfig instance from the FirebaseApp. The big challenge with RemoteConfig is the SDK to require a browser context to be able to start. My solution is to create the remoteConfig instance in theonMountlifecycle hook. The downside is the need for the app to be passed in the context.RemoteConfigString: Fetch a string variable from RemoteConfigRemoteConfigNumber: Fetch a number variable from RemoteConfigRemoteConfigBoolean: Fetch a boolean variable from RemoteConfigRemoteConfigValue: Fetch a variable from RemoteConfig in the raw Value formatThese components support the default value configured in RemoteConfig when configured.