The route should be accessible, as it is correctly displayed in the Swagger documentation.
Actual Behavior
Attempting to access this route returns a 404 error.
Solution
The route becomes accessible if the following adjustments are made:
Update the subrouter registration:
app.route("/api/v1/users", usersHono);
Adjust the path format in the UserWebsocketRoute:
path: "/{userId}/websocket",
Additional Context
It seems that the trailing slash in the route definition (/api/v1/users/) and the missing leading slash in UserWebsocketRoute's path may be causing the routing issue.
Issue Summary
When using the following code to set up a route, the route appears in the Swagger documentation but results in a 404 error when accessed:
Expected Behavior
The route should be accessible, as it is correctly displayed in the Swagger documentation.
Actual Behavior
Attempting to access this route returns a 404 error.
Solution
The route becomes accessible if the following adjustments are made:
Update the subrouter registration:
Adjust the path format in the
UserWebsocketRoute
:Additional Context
It seems that the trailing slash in the route definition (
/api/v1/users/
) and the missing leading slash inUserWebsocketRoute
's path may be causing the routing issue.