feat: populate home screen with AppRegistry entries

[tido64]

Description

When components is missing or empty in app.json, we attempt to populate the home screen with entries found in the AppRegistry.

Resolves #189.

Platforms affected

• Android
• iOS
• macOS
• Windows

Test plan

1. Run yarn in example folder

   cd example
   yarn
   

2. Remove components from app.json:

   diff --git a/example/app.json b/example/app.json
   index 8463354..0d50753 100644
   --- a/example/app.json
   +++ b/example/app.json
   @@ -1,17 +1,6 @@
    {
      "name": "Example",
      "displayName": "Example",
   -  "components": [
   -    {
   -      "appKey": "Example",
   -      "displayName": "App"
   -    },
   -    {
   -      "appKey": "Example",
   -      "displayName": "App (modal)",
   -      "presentationStyle": "modal"
   -    }
   -  ],
      "resources": {
        "android": [
          "dist/res",

3. Build and run test app, e.g. for iOS:

   pod install --project-directory=ios
   yarn ios
   
   # In a separate terminal:
   yarn start
   

Remaining work

• Since this solution relies on JSI, we cannot reuse it on Android without requiring the user to install NDK. React Native currently does not have this requirement, and we don't want to add extra dependencies. A solution would be to build and ship AARs like react-native does, but this will have to be a separate PR.

[acoates-ms]

What happens if you get here when webdebugging?

[tido64]

This is a good call. The test app is broken due to an unrelated issue fixed in #493.

With the fix applied, what happens is that we return early with an empty array here:

react-native-test-app/common/AppRegistry.cpp

Lines 22 to 25 in 09fca86

	auto global = runtime.global();
	if (!global.hasProperty(runtime, kFbBatchedBridgeId)) {
	return result;
	}

I'm hesitant to implement a fallback for this, especially when web debugging might go away soon. Unless you have any suggestions, I'm going to leave this as is.

[arazabishov]

Could we send the list of components over the bridge instead? (to include android)

[tido64]

Could we send the list of components over the bridge instead? (to include android)

We could, but that requires changes to the JS. I'm not sure how we can achieve that without requiring users to add an extra import or similar.

[tom-un]

If there is a list of componetns in the manifest, wouldn't you want to call this with enable: true?

[tido64]

The property is for deciding whether the menu item should be enabled. Since the bridge hasn't been initialized yet, we should prevent them from being clicked. They get enabled when it is:

react-native-test-app/macos/ReactTestApp/AppDelegate.swift

Line 83 in fae8b9f

strongSelf.reactMenu.items.forEach { $0.isEnabled = true }

[github-actions]

🎉 This PR is included in version 0.8.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀