Support get real route path in middleware

[seepine]

What is the feature you are proposing?

Now

app.use(async (c, next) => {
    console.log(c.req.method, c.req.routePath, c.req.path, c.req.url)
    //             GET           /*            /user/1      http://127.0.0.1:3000/user/1

}

app.get("/user/:id", ...)

// and curl
// curl http://127.0.0.1:3000/user/1

Want to

    console.log(c.req.routePath)
    //          /user/:id

[yusukebe]

Hi @seepine

Now, you can use Route helper: https://hono.dev/docs/helpers/route

import { Hono } from 'hono'
import { routePath } from 'hono/route'

const app = new Hono()

app.get('/user/:id', (c) => {
  console.log(routePath(c)) // `/user/:id`
  return c.json({})
})

export default app

[seepine]

@yusukebe Hi, i want to get real routePath in middleware, not the route handler

curl http://127.0.0.1:3000/user/1

const app = new Hono()

app.use(async (c, next) => {
    console.log(routePath(c))  // `/*`
    console.log(c.req.path)    // `/user/1`
    await next()
})

app.get('/user/:id', (c) => {
  return c.json({})
})

export default app

[yusukebe]

@seepine

I see. However, you can't retrieve /user/:id in the middleware using that syntax because the middleware knows only the path that it matched.

If you put the middleware with a path like the following, it displays /user/:id.

app.get(
  '/user/:id',
  async (c, next) => {
    console.log(routePath(c)) // /user/:id
    await next()
  },
  (c) => {
    return c.json({})
  }
)

[pradeepbgs]

Well we can add original path in context itself while creating context .
Isn't?

when we do const machedResults = this.router.match()
const c = new Context ()

Here we just need to make sure router returns path+handlers both and give original path in context

[ex0ns]

In case it can help someone as I don't remember this was documented anywhere, calling getRoutePath after next() will give you the proper route:

const before =  getRoutePath(c);
await next();
const after = getRoutePath(c);

[usualoma]

Hi @ex0ns, thanks for the comment.

#4196 (comment)

Ah, that might need to be fixed as a bug. I think we need a more formal way to get it.

[pradeepbgs]

Hi @ex0ns, thanks for the comment.

#4196 (comment)

Ah, that might need to be fixed as a bug. I think we need a more formal way to get it.

We already send matchedResults in context while creating, The easiest way is to create a method in context class and there we have matchedResults access, we just need to traverse last arrays and get the path, isn't?

[seepine]

example

import { routePath } from 'hono/route'

app.use('*', (c, next) => {
  console.log(routePath(c)) // '*'
  console.log(routePath(c, -1)) // '/posts/:id'
  return next()
})

app.get('/posts/:id', (c) => {
  return c.text(routePath(c)) // '/posts/:id'
})