You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue description:
I'm encountering a problem with the hono/zod-openapi package where path parameters are not recognized when they're used in a sub-application routing configuration. Here's a detailed description of the issue:
@hono/zod-openapi: 0.12.1
Not working (sub-application with parameterized route):
In this configuration, the path parameter matchOngoingId does not get recognized and results in an error when trying to access the parameter in the sub-application.
Working (direct application route with parameter):
constappGet=newHono();constroute=createRoute({path: "/{matchOngoingId}/get",// This works when directly placed heremethod: "get",description: "test",request: {params: z.object({matchOngoingId: z.string(),}),},// ...});constapp=newHono();app.route("/",appGet);
Here, when the parameterized route is directly set in the main application, it works perfectly fine.
Expected behavior:
I would expect the path parameters to be captured regardless of whether they are defined in the main application or a sub-application.
Actual behavior:
The path parameters are not being captured when set via a sub-application.
It seems like a bug with routing in sub-applications. Could you please look into this?
Thank you!
The text was updated successfully, but these errors were encountered:
This is not a bug. The following format is not supported. We don't have a plan to implement it because to support it, we have to change the hono core code. Thanks.
Issue description:
I'm encountering a problem with the
hono/zod-openapi
package where path parameters are not recognized when they're used in a sub-application routing configuration. Here's a detailed description of the issue:Not working (sub-application with parameterized route):
In this configuration, the path parameter
matchOngoingId
does not get recognized and results in an error when trying to access the parameter in the sub-application.Working (direct application route with parameter):
Here, when the parameterized route is directly set in the main application, it works perfectly fine.
Expected behavior:
I would expect the path parameters to be captured regardless of whether they are defined in the main application or a sub-application.
Actual behavior:
The path parameters are not being captured when set via a sub-application.
It seems like a bug with routing in sub-applications. Could you please look into this?
Thank you!
The text was updated successfully, but these errors were encountered: