[Alokxyz1112]

GoRouterState.name and GoRouterState.path are nullable, and the docs only said they can be null for the top level redirect, which left people guessing (see the issue). Going through every place that builds a GoRouterState, they are left null in:

• RouteConfiguration.buildTopLevelGoRouterState, used for the top level GoRouter.redirect and onException
• ShellRouteMatch.buildState, since a ShellRoute / StatefulShellRoute has no path of its own
• RouteBuilder._buildErrorState, used for the error page

name is also null when the GoRoute just has no name. This updates both doc comments to list those cases. Added a pending changelog entry (patch).

Fixes flutter/flutter#121086

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

Tests: exempt, this only changes doc comments.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. If both you and the PR author believe this PR qualifies for a test exemption, escalate to the tech lead for the changed area to review and apply the test-exempt label. All reviewers should feel empowered to ask for tests before escalating.

[gemini-code-assist]

Code Review

This pull request updates the documentation for GoRouterState.name and GoRouterState.path to clarify the specific scenarios in which these properties are null, and adds a corresponding changelog entry. The feedback suggests a grammatical correction to ensure proper subject-verb agreement in the updated documentation for GoRouterState.path.

[gemini-code-assist]

The phrase 'a [ShellRoute] or [StatefulShellRoute]' is singular disjunctive, so the parenthetical clause should use singular verbs and pronouns ('has' and 'its') for proper subject-verb agreement.

Suggested change

	/// the state built for a [ShellRoute] or [StatefulShellRoute] (which have no
	/// path of their own), and the state used for the error page.
	/// the state built for a [ShellRoute] or [StatefulShellRoute] (which has no
	/// path of its own), and the state used for the error page.