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
Regarding the google API design custom methods, the issue has been resolved in PR #1988.
However, this solution is not complete as it does not allow a custom method to be appended after a path parameter.
For example in https://service.name/v1/some/resource/{name}:customVerb, the {name} is route parameter, the :customVerb is not route parameter and only is a simple string.
// curl -v -X POST "http://localhost:8088/v1/some/resource/name:undelete"funcmain() {
e:=echo.New()
// route path as Cloud API "custom method"// https://cloud.google.com/apis/design/custom_methodse.POST("/v1/some/resource/:name\\:undelete", func(c echo.Context) error {
name:=c.Param("name")
resp:=fmt.Sprintf("%s undeleted", name)
returnc.String(200, resp)
})
log.Fatal(e.Start(":8088"))
}
The text was updated successfully, but these errors were encountered:
Kurichi
changed the title
Allow escaped : char in route path after path-param
Allow escaped : char in route path after route parameter
Mar 16, 2025
Regarding the google API design custom methods, the issue has been resolved in PR #1988.
However, this solution is not complete as it does not allow a custom method to be appended after a path parameter.
For example in
https://service.name/v1/some/resource/{name}:customVerb
, the {name} is route parameter, the :customVerb is not route parameter and only is a simple string.The text was updated successfully, but these errors were encountered: