the router not overrite about gin HOT 5 CLOSED

gin uses httprouter as HTTP request router, if you check "Named parameters" at the link below, you will see that this is how httprouter is designed, by explicit matches, so you can't have /user/new and /user/:user.

https://github.com/julienschmidt/httprouter#named-parameters

from gin.

Just to correct myself, you can't have both on the same HTTP method, so you can have

r.GET("/user/:user", showUser)
r.POST("/user/new", newUser)

But assuming you want to return html and json formats of the same user, you may do this

r.GET("/user/:user", showUserHTML)
r.GET("/user/:user/json", showUserJSON)

from gin.

@allochi let's develop infinite middlewares. here is your solution:

package gin

func DefaultParam(p string, f HandlerFunc) HandlerFunc {
    return func(c *Context) {
        if c.Params.ByName("name") == p {
            f(c)
            c.index = AbortIndex
        }
    }
}

and you use it like this:

r.GET(
    "/test/:name",
    gin.DefaultParam(
        "json",
        func(c *gin.Context) {
            c.String(400, "default param detected")
        }),
    func(c *gin.Context) {
        c.String(200, "the param is "+c.Params.ByName("name"))
    })

from gin.

Smart 😄, but too much, I would probably just switch that in the handler, specially if I have more than one value to check.

I was just explaining that httprouter uses explicit matches, so it's not a bug in gin.

from gin.

Of course, the best way to handle this is to use a Switch. With my example just wanted to show how flexible is Gin and how to design an alternative when you can't modify your handlers. We all know that combining two handlers in one hurt our eyes.

So... because Ali explained why this error is not part of Gin, and I posted a small middleware to help get around, I'm closing the issue.

from gin.