Refactor Router and ModuleLoader: Decouple module loading from route building #409
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.
ModuleLoaderno longer executes module route closures or builds runtime routes.It only loads module
configs/dependenciesand returns module route definition closures.RouteBuilderis responsible for executing those closures using the existing Route DSL collectorand producing the final runtime routes array that
Routerexpects today.IMPORTANT:
RouteController/Routerstill operate on route arrays at this stage.Routeobject-centric internal representation will be done in a follow-up,because it requires coordinated changes across
Routermatching,RouteControllerstate and helpers.