Repository navigation
/_browser routes appear in application Routes UI even though corresponding controllers are not in /app #2577
Description
Describe the bug
In the Routes section of a Wheels application, several /_browser routes are displayed under the application routes list. Examples include:
/_browser/home/_browser/login/_browser/dashboard/_browser/login-as
However, the corresponding controllers and views do not exist in the application's /app directory. These routes are internal browser test fixture routes and are not part of the developer's application code.
This can be confusing because the Routes UI suggests that these are application-defined routes.
To Reproduce
Steps to reproduce the behavior:
- Create or run a Wheels application.
- Navigate to the Routes section.
- Observe the
/_browserroutes listed under application routes. - Check the
/app/controllersand/app/viewsdirectories. - Note that no corresponding files exist in the application.
Expected behavior
One of the following should happen:
- Internal
/_browserroutes should not be shown in the application Routes UI. - These routes should be displayed in the “Internal” section.
- If they are no longer needed, they should be removed entirely.
Screenshots
Desktop:
- OS: Any
Additional context
These routes appear to be defined for browser testing and point to framework-provided controllers rather than application controllers.
Showing them alongside application routes:
- Creates confusion for developers
- Makes the route list noisier
- Blurs the distinction between framework internals and user-defined routes
Suggested improvement:
- Move these routes to an internal routes file if they are framework-owned.
- Exclude them from the application Routes UI.
- Alternatively, display them under the “Internal” section.
Activity
wheels-bot commentedon May 11, 2026
Wheels Bot — Triage
Classified as bug.
Suspected layer
router— seevendor/wheels/public/views/routes.cfmfor the categorization logic.Fix sketch
The Routes UI splits routes into "Internal" vs "Application" using a single condition in
vendor/wheels/public/views/routes.cfm(line 12):The
/_browserfixture routes are registered with controllers likeBrowserTestHomeandBrowserTestSessions(seevendor/wheels/public/browser-fixtures/routes.cfm). Neither controller name matcheswheels.public, and none of their patterns match/wheels/app/tests, so they fall through toappRoutes. The fix is to extend the condition to also match routes whose pattern starts with/_browser— a one-line change inroutes.cfm.Confidence:
highThe reproduction steps are clear, the screenshot confirms the symptom, the faulty condition is pinpointed to one file and one line, and the fix is mechanical with no design trade-offs or cross-engine concerns.
<!-- wheels-bot:triage:2577 -->
<!-- wheels-bot:triage-class:bug -->
<!-- wheels-bot:triage-confidence:high -->
wheels-bot commentedon May 11, 2026
Wheels Bot — Fix proposed
Draft PR: #2588
Spec:
vendor/wheels/tests/specs/view/routesViewBrowserFixturesSpec.cfc— failing → passingImplementation:
vendor/wheels/public/views/routes.cfmA human review is required before merge. Reviewer A and Reviewer B will weigh in shortly. Doc updates (MDX guides,
.ai/wheels/,CLAUDE.md) are handled separately bybot-update-docs.yml.