Linking path assertion needs to account for nested screens.

[EvanBacon]

Current behavior

If you have an app with routes /home and /profile, each with their own navigator, then you'll get a collision error on the navigators.

Here is the linking configuration:

{
    "prefixes": [
        "http://localhost:19000/"
    ],
    "config": {
        "screens": {
            "(stack)": {
                "path": "",
                "screens": {
                    "home": {
                        "path": "home"
                    }
                }
            },
            "(tab)": {
                "path": "",
                "screens": {
                    "profile": {
                        "path": "profile"
                    }
                }
            }
        }
    }
}

(stack) and (tab) both technically match /, but due to the nested children / can never be matched. Commenting our this assertion fixes the issue, meaning we probably need to update the check to account for screens.

Expected behavior

A user should be able to navigate to /profile and /home given the above configuration.

Reproduction

https://snack.expo.dev/@bacon/conflicting-screen-bug

Platform

• Android
• iOS
• Web
• Windows
• MacOS

Packages

• @react-navigation/​bottom-tabs
• @react-navigation/​drawer
• @react-navigation/​material-bottom-tabs
• @react-navigation/​material-top-tabs
• @react-navigation/​stack
• @react-navigation/​native-stack

Environment

@react-navigation/native: ^6.0.12 (latest)

[github-actions]

Couldn't find version numbers for the following packages in the issue:

• @react-navigation/native

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.