You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
initial project with elysia bun create elysia app
install both tRPC and swagger plug-ins bun add @elysiajs/swagger @elysiajs/trpc @trpc/server @elysiajs/websocket
apply both middlewares
// index.ts
import {Elysia} from 'elysia';
import {appRouter} from "./router";
import {trpc} from "@elysiajs/trpc";
import swagger from "@elysiajs/swagger";
const app = new Elysia();
app.use(swagger())
app.use(trpc(appRouter))
app.listen(3000, () => {
console.log('Server is running on http://localhost:3000');
});
I see every handle equavivalent in my swagger docs (GET for query and POST for mutation)
What do you see instead?
Empty docs
Additional information
I used the setup of chaos middlewares and nginx + traefik setup to see the docs with elysia. But it's not tRPC server anymore, it's typed REST. Is it possible to fix middleware or something?
Here's a repo with this crazy setup (I think it done wrong):
What version of Elysia is running?
"version": "1.1.26"
What platform is your computer?
Microsoft Windows NT 10.0.19044.0 x64
What steps can reproduce the bug?
initial project with elysia
bun create elysia app
install both tRPC and swagger plug-ins
bun add @elysiajs/swagger @elysiajs/trpc @trpc/server @elysiajs/websocket
apply both middlewares
What is the expected behavior?
I see every handle equavivalent in my swagger docs (GET for query and POST for mutation)
What do you see instead?
Empty docs
Additional information
I used the setup of chaos middlewares and nginx + traefik setup to see the docs with elysia. But it's not tRPC server anymore, it's typed REST. Is it possible to fix middleware or something?
Here's a repo with this crazy setup (I think it done wrong):
https://gitlab.com/manazoid/trpc-swagger-for-elysiajs
Have you try removing the
node_modules
andbun.lockb
and try again yet?yes
The text was updated successfully, but these errors were encountered: