This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Open
Conversation
… which has peer dependency problems
Co-authored-by: Donny/강동윤 <kdy1997.dev@gmail.com>
return an unknown error even if not TRPCError
mathmach
approved these changes
Sep 19, 2024
|
awesome! how to make it works with next 14? import {createContext} from '@/utils/trpc/server';
import {createOpenApiNextHandler} from 'trpc-openapi';
import {appRouter} from "@/app/api/v1/trpc-router";
const handler = (request: Request, res: Response) => {
return createOpenApiNextHandler({
router: appRouter,
createContext: createContext as any,
})(request as any, res as any);
};
export {
handler as DELETE,
handler as GET,
handler as OPTIONS,
handler as PATCH,
handler as POST,
handler as PUT
};but when i call an endpoint i have this: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Guessing this should be merged into a
nextbranch, but this brings support fortrpc @next(v11).Details of this PR are in kdy1#2. This was built on top of the work done by @kdy1, as referenced in #434