Anthony Skorupskyy

How a found a little way to make this work: Below is a pure type that does not care about the contents of route implementation. For now I am just...

I tried the same thing but with `@hono/zod-openapi`, and here's what I got ```typescript const route = createRoute({ method: 'get', path: '/hello', request: { params: z.object({ test: z.string() }), },...

I'll make a project and tag you in a couple hrs. I found a hack around original Hono type behavior but this would be nice to have as a part...

> Hi @askorupskyy > > Is the matter resolved? If not, please provide a minimal project to reproduce it. I'll investigate. https://github.com/askorupskyy/hono-rpc-types I created a simple project that explains the...

I read through some more issues and I think using my proposal would also fix #1921. Seems like one of the cases I covered in the README to my repo

@yusukebe Nx in my case is just used to demonstate some of the bugs the current type system might cause. The main problem is Hono client needs to infer all...

This syntax would work better: ```typescript // declare a router const createUserRouter = createRouter({ method: 'POST', input: // either a TS type or a zod object output: // just a...

@yusukebe thank you so much! i did not initially realize zod-openapi resolves this matter completely

@yusukebe I spoke with a few more people encountering the same issue as I did (not only with Hono, but tRPC, Elysia and etc), so I wrote a little library...

Sorry for disappearing guys, a lot of stuff happened. Either way, I found a way to make everything work, and after quite a long pause I am able to continue...