Fix linking path

[ercote]

Motivation

At the moment, a linking url without a path (with or without an ending slash) cannot match the linking configuration, as it is ignored.

Consider the following linking configuration:

{
  prefixes: ['https://myapp.com/'],
  config: {
    screens: {
      MyScreen: '',
    },
  },
};

If the received linking url is equal to https://myapp.com/ it won't be matching MyScreen as the empty path is ignore. To be able to match an empty path, we need to change the path validation (see change in useLinking.native.tsx).

The getStateFromPath function is already able to match an empty string. Tests have been added to clearly expose the expected behaviour.

Test plan

Use a deeplink url without a path in your app and match that deeplink in your linking configuration using an empty path.

[github-actions]

Hey ercote! Thanks for opening your first pull request in this repo. If you haven't already, make sure to read our contribution guidelines.

[netlify]

✅ Deploy Preview for react-navigation-example ready!

Name	Link
🔨 Latest commit	e7ddaf6
🔍 Latest deploy log	https://app.netlify.com/sites/react-navigation-example/deploys/62d82a46ef3ee5000922bab7
😎 Deploy Preview	https://deploy-preview-10708--react-navigation-example.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[satya164]

Thanks for the PR

[intergalacticspacehighway]

@satya164 @ercote this change resets the navigation state if the app is redirected from another app.

IMO root URL ("" or /) deeplink should be handled when app is opened first time, if it's already opened then it should not reset the navigation state. I can do a PR. Let me know if this is expected.

You can check the below video to see the usecase. Navigation resets on redirection from another app.

RPReplay_Final1664352656.MP4

[github-actions]

Hey! This issue is closed and isn't watched by the core team. You are welcome to discuss the issue with others in this thread, but if you think this issue is still valid and needs to be tracked, please open a new issue with a repro.