[go_router_builder] Update route_config.dart to allow percent-encoding path

[AlexeyBukin]

Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.

List which issues are fixed by this PR. You must list at least one issue.

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

[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 you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

[gemini-code-assist]

Code Review

This pull request attempts to fix an issue with percent-encoding in path patterns by using Uri.encodeFull. While this works for spaces, it's an incomplete solution as it doesn't handle other characters that should be encoded in path segments (like +). I've suggested a more robust approach that correctly encodes all static path segments while leaving parameter placeholders untouched.

[gemini-code-assist]

Using Uri.encodeFull is an improvement for paths with spaces, but it's not a complete solution. It doesn't encode other characters that should be percent-encoded in a path segment (like +), which can lead to malformed or ambiguous URLs.

A more robust approach is to split the path into segments, encode each static segment individually, and then rejoin them. This ensures that all special characters in static path segments are correctly encoded, while parameter placeholders are preserved for patternToPath.

Suggested change

	final String location = patternToPath(Uri.encodeFull(_basePathForLocation), pathParameters);
	final String location = patternToPath(_basePathForLocation.split('/').map((String s) => s.startsWith(':') ? s : Uri.encodeComponent(s)).join('/'), pathParameters);

[AlexeyBukin]

Basically we Uri.encodeComponent every path parameter but the original url must be ascii. That's strange.
Let's say we have a path parameter id runtime resolving to пяты (id = 5 in belarussian).

@TypedGoRoute<ZoneRoute>(path: '/прывітанне/:id') // pass id = `пяты`
...

Resolving before pr: /прывітанне/%D0%BF%D1%8F%D1%82%D1%8B (Partly encoded?)

Resolving after pr: /%D0%BF%D1%80%D1%8B%D0%B2%D1%96%D1%82%D0%B0%D0%BD%D0%BD%D0%B5/%D0%BF%D1%8F%D1%82%D1%8B (Fully encoded!)