Taku Amano

If we solve this on the application side, I think the following is one way to do it. https://github.com/honojs/hono/pull/4336

That's true, I agree with that opinion. > In the getPath option case, it should be inside hono-base.ts, but for getRequest, it is not 100% needed in hono-base.ts.

Hi @houssems. Thank you for creating a pull request! ### Should we accept thenable? When the following code was executed in Deno and "wrangler," a message was displayed. Bun caused...

Hi @mjeanroy, Thanks for the report. Apologies for the delayed response. Would you be able to share the code or project that reproduces the problematic behavior?

Hi @Tc-001 Thank you for your suggestion. Hi @yusukebe To obtain the "basePath", I think the following approaches would be appropriate. https://github.com/honojs/hono/pull/4204 * Save basePath when registering the route *...

It works as follows. ```ts import { Hono } from 'hono' import { basePath, routePath } from 'hono/route' const app = new Hono() const subApp = new Hono() subApp.get('/:id', (c)...

Hi @Tc-001. Thank you for your feedback. You're right. I updated #4204 so that when parameters are taken, the resolved path is output. The method names are temporary for now,...

### `Component` class In React, the `Component` class is currently a Legacy API. https://react.dev/reference/react/Component ### Can Hono support `Component` class? Yes, it is technically possible. The most basic feature can...

Hi @gaetan-puleo Thanks for creating the issue and commenting. We will consider it.

Hi @yusukebe In terms of implementation feasibility, I think it could be done with an approach like #2933. However, looking at the way "hono" and "honox" are currently used, I...