Request: update example app to asynchronously open realm

The current example initialises the realm in a seperate file (module) which is then exported and imported into the other files:

//realm.js
export default new Realm({schema: [Todo, TodoList]});

However, the docs state:

This is typically not recommended as it blocks and could potentially be a time consuming operation, especially if there are migrations to run or if the realm is synchronized and you don’t want to risk modifying data before it’s been completely downloaded. https://realm.io/docs/javascript/latest/#synchronously-opening-realms

Can the example app please be updated to show how to open the realm (with Realm.open) in a seperate file (module) which is then imported into the other components?

[kraenhansen]

@MrHubble we’re working on an example app for React Native, until it’s merged you can have a look at the branch for the PR: https://github.com/realm/my-first-realm-app/tree/eric-rn/react-native/QueryBasedSync/ToDo

Here we’re using new Realm(config) to open a Realm instance when the user authenticates. Then we pass the realm instance to the apps router (in our case react-native-router-flux) to change into a “logged in” scene: https://github.com/realm/my-first-realm-app/blob/eric-rn/react-native/QueryBasedSync/ToDo/src/components/LoginForm.js#L61-L68

I hope this gives an idea on how this can be accomplished and I hope that we’ll soon be able to get better React Native examples published.

[kneth]

Every new Realm or Realm.open must be paired with close. As React Native runs as 32 bit, you can easily run into memory issues (600-700 MB Realm files). It can be a good idea to compact the Realm when your app is launching (shouldCompactOnLaunch - https://realm.io/docs/javascript/2.20.0/api/Realm.html#~Configuration).