Yusuke Wada
Yusuke Wada
@vickyRathee I can't reproduce it. Please provide a minimal project to reproduce it if you want we help you.
@mansimransingh Thank you for the PR! Hi @monoald, Can you review this?
Hi @cjnoname Do you think this is a problem only for AWS Lambda?
@cjnoname Can you provide a minimal project to reproduce the issue and an instruction?
@cjnoname > Hey mate, sorry—I’ve been quite busy with this. No problem! > There’s no way to replicate it locally. That's the pain point of AWS Lambda, and I'm not...
@watany-dev Thanks!
Hey. Now I think we can close this issue. Thank you.
Hi @mecab Thank you for raising the issue. This is like a bug, but it is a not implemented thing rather than a bug. We can't fix it right now,...
Hi @ruimaciel As @EdamAme-x said, it can support a wildcard parameter with regexp like the following: ```ts app.get('/posts/:path{.+}', async (c) => { return c.text(c.req.param("path")) }) ```
@EdamAme-x Indeed, supporting `/:parameter*` will decrease the user's confusion. But, hmm. In my opinion, it's okay whether we do it or not.