[go_router] Fix relative navigation after imperative navigation

[Boulea7]

Relative navigation after an imperative push currently resolves against the underlying route information instead of the visible imperative route. This updates go, push, pushReplacement, and replace to resolve ./ locations against the imperative top match, while preserving the existing behavior for other locations. Regression coverage includes query parameters and fragments.

This revisits and completes the fix proposed in #11726. Thank you @NadeemIqbal for the earlier investigation and implementation.

Fixes flutter/flutter#182441.

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.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

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. ↩ ↩²

[gemini-code-assist]

Code Review

This pull request updates GoRouter to resolve relative locations starting with ./ against the last imperatively-pushed route match for the go, push, pushReplacement, and replace methods, and adds corresponding regression tests. The review feedback suggests extending this resolution logic to also support relative paths starting with ../.

[chunhtai]

Hi @Boulea7 , just want to double check on the correct behavior, when using imperative API, the URL won't reflect the url of the pushed route. so for example if you are currently on /home but do a push /page1, the url bar will still show as /home, in that case the current behavior is correct because when you do relative navigation, it should be based on current url in url bar.