fix: loadRoutesFrom() not loading routes added after DispatcherFactory construction
#301
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.
Problem
Routes registered via
loadRoutesFrom()in service providerboot()methods are not loaded.Cause
DispatcherFactorycaptures the route file list in its constructor:But
loadRoutesFrom()adds files toRouteFileCollectorduring service provider boot(), which happens after theDispatcherFactorymay have been constructed. The captured list is stale, so late-added routes are never loaded.It looks like lazy loading via
initRoutes()was intended to defer route loading, but capturing the route file list in the constructor defeats this purpose.Solution
Move route file fetching from the constructor to initRoutes():
This ensures route files are fetched when
getRouter()is first called, after all service providers have had a chance to registertheir routes.
Performance
No impact. Route initialization happens once per worker process at startup. The fix adds one container lookup that executes once during worker startup.
Changes
initRoutes()