Skip to content
Discussion options

You must be logged in to vote

Hi @SSam0419! I'm Dosu and I’m helping the orpc team.

orpc does not natively support dynamic parameters in the prefix (like /api/{workspaceId}) for routers, which is why your current approach results in 404 and matched is always false. The framework expects static prefixes, and dynamic path parameters must be defined directly in the route path and input schema, not in the prefix option. This is a known limitation and there is an open discussion and draft proposal about supporting this feature natively, but it is not available yet [discussion].

The recommended workaround is to use an external router (such as Hono) to extract the dynamic parameter from the path, then pass it as both the pr…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by SSam0419
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant