Skip to content

Check the chained resolver's answer and use the public router - #22

Merged
imanimanyara merged 2 commits into
mainfrom
fix/check-resolver-answer-public-router
Oct 5, 2026
Merged

imanimanyara merged 2 commits into
mainfrom
fix/check-resolver-answer-public-router

Conversation

@imanimanyara

Copy link
Copy Markdown
Member

RouteNameFallback passed the previous missing-route resolver's answer
through unchecked, so a non-string answer was a TypeError inside route()
under strict_types; it now reads as not resolved. The scoped-route check
also read the URL generator's protected route collection through a bound
closure, although Router::has() answers the same question publicly.
register() takes the router as an optional second argument, so the old
single-argument call keeps working.

RouteNameFallback passed the previous missing-route resolver's answer
through unchecked, so a non-string answer was a TypeError inside route()
under strict_types; it now reads as not resolved. The scoped-route check
also read the URL generator's protected route collection through a bound
closure, although Router::has() answers the same question publicly.
register() takes the router as an optional second argument, so the old
single-argument call keeps working.
Copilot AI balanced review requested due to automatic review settings October 5, 2026 09:27

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

CI's Rector run rejected the two tests added in this branch for using
inline fully qualified UrlGenerator and RouteCollection. Import them, as
Rector's import-names rule and the shared Pint ordering require.
@imanimanyara
imanimanyara merged commit 4d70779 into main Oct 5, 2026
6 checks passed
@imanimanyara
imanimanyara deleted the fix/check-resolver-answer-public-router branch October 5, 2026 09:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants