Skip to content

Conversation

@unnoq
Copy link
Member

@unnoq unnoq commented Jul 12, 2025

Summary by CodeRabbit

  • Documentation

    • Added a TypeScript code example to clarify how to use the .meta property with route metadata in tRPC procedures for OpenAPI integration.
  • Bug Fixes

    • Adjusted the structure of metadata for tRPC procedures to nest route information under a route key, improving consistency and clarity.
  • Tests

    • Enhanced tests to verify the updated metadata structure and added layered error handling validation for invalid procedure calls.

@vercel
Copy link

vercel bot commented Jul 12, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
orpc ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 15, 2025 0:18am

@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Jul 12, 2025
@coderabbitai
Copy link

coderabbitai bot commented Jul 12, 2025

Walkthrough

The changes update the handling and structure of metadata for tRPC procedures being converted to oRPC procedures. The meta property is now expected to contain a nested route object. Type definitions, test cases, and documentation are updated to reflect and validate this new metadata structure, and the get utility function is generalized.

Changes

File(s) Change Summary
apps/content/docs/openapi/integrations/trpc.md Added a TypeScript code snippet to demonstrate the new .meta structure with a nested route property.
packages/shared/src/object.ts Broadened the get function's parameter type from object to unknown.
packages/trpc/src/to-orpc-router.ts Updated experimental_ORPCMeta to have an optional route property; now uses get to access route.
packages/trpc/src/to-orpc-router.test.ts Adjusted tests for new nested route metadata; added error cause validation for invalid input cases.
packages/trpc/tests/shared.ts Changed trpcRouter's metadata structure for nested.ping to use a nested route object.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant tRPC Procedure
    participant toORPCProcedure
    participant oRPC Procedure

    Developer->>tRPC Procedure: Define procedure with .meta({ route: { ... } })
    tRPC Procedure->>toORPCProcedure: Pass procedure for conversion
    toORPCProcedure->>toORPCProcedure: Use get(meta, ['route']) to extract route
    toORPCProcedure->>oRPC Procedure: Create oRPC procedure with route metadata
Loading

Possibly related PRs

  • unnoq/orpc#699: Updates to to-orpc-router.ts and related files for converting tRPC routers to oRPC routers, including metadata structure changes and associated tests.

Suggested labels

size:L

Poem

In the warren of code, where the routers hop,
Metadata now nests, with a route at the top.
Tests are adjusted, types freshly spun,
The get function’s broadened—now any can run!
With docs and examples, the path is now clear,
🐇 Cheers to new structure—let’s give a big cheer!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 17a1d9e and 96f192f.

📒 Files selected for processing (1)
  • packages/trpc/src/to-orpc-router.test.ts (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/trpc/src/to-orpc-router.test.ts
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: publish-commit
  • GitHub Check: lint
  • GitHub Check: Analyze (javascript-typescript)
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @unnoq, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a breaking change by restructuring the ORPCMeta interface within the tRPC integration. The primary goal is to improve the organization of metadata by nesting route-related information under a dedicated route property. This change necessitates updates to how route metadata is defined in tRPC procedures and how it's accessed internally, with corresponding documentation and test updates to ensure compatibility and correct error handling.

Highlights

  • ORPCMeta Restructuring: The experimental_ORPCMeta interface has been refactored to nest route-specific metadata under a route property, improving the overall organization of metadata for tRPC procedures.
  • Metadata Access Update: The internal logic responsible for extracting route metadata from tRPC procedures has been updated to correctly access the newly nested route property within the ORPCMeta structure.
  • Documentation & Test Alignment: Existing documentation and test cases have been updated to reflect the new ORPCMeta structure, ensuring consistency and providing clear examples for proper usage.
  • Error Handling Enhancement: A new test case has been added to verify robust error handling for input validation failures, specifically ensuring that ORPCError instances correctly wrap underlying TRPCError and ZodError instances.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@codecov
Copy link

codecov bot commented Jul 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors ORPCMeta to nest route-specific information under a route property, which is a breaking change. The changes are consistently applied across documentation, tests, and implementation. The get utility is also improved for better type safety.

My review identifies one high-severity issue regarding type safety in to-orpc-router.ts where a value of type unknown is assigned to a property expecting an object, which could lead to runtime errors. I've provided a suggestion to fix this using a type guard.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Jul 12, 2025

More templates

@orpc/arktype

npm i https://pkg.pr.new/@orpc/arktype@758

@orpc/client

npm i https://pkg.pr.new/@orpc/client@758

@orpc/contract

npm i https://pkg.pr.new/@orpc/contract@758

@orpc/experimental-durable-event-iterator

npm i https://pkg.pr.new/@orpc/experimental-durable-event-iterator@758

@orpc/hey-api

npm i https://pkg.pr.new/@orpc/hey-api@758

@orpc/json-schema

npm i https://pkg.pr.new/@orpc/json-schema@758

@orpc/nest

npm i https://pkg.pr.new/@orpc/nest@758

@orpc/openapi

npm i https://pkg.pr.new/@orpc/openapi@758

@orpc/openapi-client

npm i https://pkg.pr.new/@orpc/openapi-client@758

@orpc/react

npm i https://pkg.pr.new/@orpc/react@758

@orpc/react-query

npm i https://pkg.pr.new/@orpc/react-query@758

@orpc/server

npm i https://pkg.pr.new/@orpc/server@758

@orpc/shared

npm i https://pkg.pr.new/@orpc/shared@758

@orpc/solid-query

npm i https://pkg.pr.new/@orpc/solid-query@758

@orpc/standard-server

npm i https://pkg.pr.new/@orpc/standard-server@758

@orpc/standard-server-aws-lambda

npm i https://pkg.pr.new/@orpc/standard-server-aws-lambda@758

@orpc/standard-server-fetch

npm i https://pkg.pr.new/@orpc/standard-server-fetch@758

@orpc/standard-server-node

npm i https://pkg.pr.new/@orpc/standard-server-node@758

@orpc/standard-server-peer

npm i https://pkg.pr.new/@orpc/standard-server-peer@758

@orpc/svelte-query

npm i https://pkg.pr.new/@orpc/svelte-query@758

@orpc/tanstack-query

npm i https://pkg.pr.new/@orpc/tanstack-query@758

@orpc/trpc

npm i https://pkg.pr.new/@orpc/trpc@758

@orpc/valibot

npm i https://pkg.pr.new/@orpc/valibot@758

@orpc/vue-colada

npm i https://pkg.pr.new/@orpc/vue-colada@758

@orpc/vue-query

npm i https://pkg.pr.new/@orpc/vue-query@758

@orpc/zod

npm i https://pkg.pr.new/@orpc/zod@758

commit: 96f192f

@unnoq unnoq changed the title feat(trpc)!: restructure ORPCMeta for better organization feat(trpc)!: restructure ORPCMeta + accessible lazy router Jul 13, 2025
@unnoq unnoq changed the title feat(trpc)!: restructure ORPCMeta + accessible lazy router feat(trpc): restructure ORPCMeta + accessible lazy router Jul 15, 2025
@unnoq unnoq merged commit 5049f7c into main Jul 15, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M This PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant