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
routeToRegexp currently use \w+ to match parameter, but parameter might contain /, especially at the senario of object storage service, we need provide a proxy for objects:
GET /dir1/dir2/dir3/file => (route) /{namespace}/{file}
The text was updated successfully, but these errors were encountered:
There was a plan to support route parameters with type, see #1 . And after finished this feature, I think we can add a special route parameter type, which allows contain '/'.
For now, we support writing regexp directly actually, and routeToRegexp is a helper for translate common usecasees in route, so I think you can write .+ in you route?
There was a plan to support route parameters with type, see #1 . And after finished this feature, I think we can add a special route parameter type, which allows contain '/'.
For now, we support writing regexp directly actually, and routeToRegexp is a helper for translate common usecasees in route, so I think you can write .+ in you route?
I still need named parameters in req.Params, let's track it in the typed parameters feature :)
routeToRegexp currently use
\w+
to match parameter, but parameter might contain/
, especially at the senario of object storage service, we need provide a proxy for objects:The text was updated successfully, but these errors were encountered: