[Feature Request] Remote Config

[jhuleatt]

Remote Config now supports web! Let's include it in ReactFire.

[jhuleatt]

Since Remote Config requires some top-level configuration, maybe we make a Provider component like FirebaseAppProvider:

function App() {
  <FirebaseAppProvider firebaseConfig={myConfig}>
    <RemoteConfigProvider
      minimumFetchIntervalMillis={3600000}
      defaultConfig={{ message: "welcome" }}
    >
      <MyComponent />
    </RemoteConfigProvider>
  </FirebaseAppProvider>;
}

function MyComponent() {
  const welcomeMessage = useRemoteConfigValue("message");
  return <h1>{welcomeMessage}</h1>;
}

I'm not sure how we'd lazy load the SDK in this situation, though. I guess we could return the defaultConfig values until the SDK is loaded? Could lead to flashes of content.

[jhuleatt]

FYI #170 introduces useRemoteConfig to lazy load the Remote Config SDK

[jhuleatt]

Chatted with @jamesdaniels and a couple more ideas came up:

• If a dev only wants to get one value from Remote Config (to stop UI flickering), add a noFlicker flag. Probably to the useRemoteConfigValue hook. This would only return the first value from Remote Config, and no updates.
• Similarly, if the developer wants to guarantee the value came from the server and not the local cache, have an onlyFresh (name TBD) flag

These would help hide some of the complexity of Remote Config