An alternative to fallback props of RealmProvider

[bglgwyng]

The problem of fallback props is that it forces developers to render the fallback page at the same level as RealmProvider.

Let me give you a more concrete situation.
I'm using @react-navigation/native. This library provides components like Navigator and Screen which help us deal with native pages.
In my code, RealmProvider is outside of the Navigator.

<RealmProvider fallback={Fallback}>
  <FooProvider>
    <Stack.Navigator>
      ...
    </Stack.Navigator>
  </FooProvider>
</RealmProvider>

When the Realm instance is under loading, <Stack.Navigator> get unmounted and it causes ugly blinks on the screen.
To avoid this behavior, we should keep <Stack.Navigator> mounted but it can't be achievable with the current design of RealmProvider.

So, my suggestion is

• remove fallback props of RealmProvider
• let the hooks(useQuery, useObject, etc) get suspended while the Realm instance is loading
• Developers can put the custom loading with Suspense component anywhere inside <Stack.Navigator>.