Description

This PR clarifies the fact that Navigator will always load the / route as the root of initialRoute deep links and that even simple routes like /a will be treated as deep links (this would mean two routes are pushed). This is to deter new users from trying to use this property when they could just use home or routes: { '/': (context) =>... instead. The resulting confusion can be seen in the linked issue.

Reset and clean PR of #64793 since there were issues with fork master diffs.

Related Issues

Fixes #64775

Tests

Not necessary, this is a documentation PR.

Checklist

Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I signed the CLA.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I updated/added relevant documentation (doc comments with ///).
• All existing and new tests are passing.
• The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Did any tests fail when you ran them? Please read Handling breaking changes.

• No, no existing tests failed, so this is not a breaking change.