Refactor routing core, introduce route collection and route finder to reduce router responsibilities #415
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Routing Refactor (Breaking Change)
Summary
This PR introduces a breaking refactor of the routing system as part of the 3.0.0 stabilization work.
The focus is correctness, explicit behavior, and test coverage — not redesign.
What changed (high-impact)
RouteRouteCollectionMatchedRouteRouteBuilderRouteDispatcherMatchedRoutestored onRequestcurrent_*,route_*) now read fromMatchedRouteContributors should focus review effort on the following areas:
1. Controller resolution
RouteController-based resolution is no longer used2. RouteBuilder behavior
3. Request → routing boundary
MatchedRouteis nullableWhat this PR does not do
How to review
Suggested review order:
RouteBuilderand its unit testsRouteDispatcherThis refactor affects core request flow — careful review is appreciated.
Closes #412