fix(trpc): make sure "import type" is used for type-only imports#1425
Conversation
WalkthroughWalkthroughThe recent updates in the tRPC plugin primarily involve adjustments to import declarations by eliminating the Changes
Assessment against linked issues
The changes address the main concern of importing types correctly to avoid runtime issues, but there might be a need to verify if the specific syntax ( Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Actionable comments posted: 1
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- packages/plugins/trpc/src/generator.ts (1 hunks)
Additional comments not posted (4)
packages/plugins/trpc/src/generator.ts (4)
102-111: The changes to import these entities as type-only are correct and align with TypeScript's requirements for type-only imports.
Line range hint
14-45: Thegeneratefunction is well-structured and handles its responsibilities correctly. Good job maintaining clean and readable code.
Line range hint
57-152: ThecreateAppRouterfunction is correctly implemented and effectively manages the setup of the application router and dynamic model routers.
Line range hint
154-250: BothcreateClientHelpersandgenerateModelCreateRouterfunctions are implemented correctly and handle dynamic generation based on configurations effectively.
Fixes #1405