Skip to content

Conversation

@hyoban
Copy link

@hyoban hyoban commented Jan 25, 2026

No description provided.

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@changeset-bot
Copy link

changeset-bot bot commented Jan 25, 2026

⚠️ No Changeset found

Latest commit: 5f20a24

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Jan 25, 2026

@hyoban is attempting to deploy a commit to the Hey API Team on Vercel.

A member of the Team first needs to authorize it.

@codecov
Copy link

codecov bot commented Jan 25, 2026

Codecov Report

❌ Patch coverage is 10.00000% with 288 lines in your changes missing coverage. Please review.
✅ Project coverage is 35.50%. Comparing base (81e98e4) to head (5f20a24).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...es/openapi-ts/src/plugins/@orpc/contract/plugin.ts 2.04% 239 Missing ⚠️
...es/openapi-ts/src/plugins/@orpc/contract/config.ts 32.87% 49 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3264      +/-   ##
==========================================
- Coverage   35.74%   35.50%   -0.24%     
==========================================
  Files         454      457       +3     
  Lines       34650    34970     +320     
  Branches     2475     2475              
==========================================
+ Hits        12385    12417      +32     
- Misses      22236    22524     +288     
  Partials       29       29              
Flag Coverage Δ
unittests 35.50% <10.00%> (-0.24%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Jan 25, 2026

Open in StackBlitz

@hey-api/codegen-core

npm i https://pkg.pr.new/hey-api/openapi-ts/@hey-api/codegen-core@3264

@hey-api/nuxt

npm i https://pkg.pr.new/hey-api/openapi-ts/@hey-api/nuxt@3264

@hey-api/openapi-ts

npm i https://pkg.pr.new/hey-api/openapi-ts/@hey-api/openapi-ts@3264

@hey-api/types

npm i https://pkg.pr.new/hey-api/openapi-ts/@hey-api/types@3264

@hey-api/vite-plugin

npm i https://pkg.pr.new/hey-api/openapi-ts/@hey-api/vite-plugin@3264

commit: bfd9c45

*
* @default (id) => `${id}Contract`
*/
contractNameBuilder?: (operationId: string) => string;
Copy link
Member

Choose a reason for hiding this comment

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

The following current options:

  • contractNameBuilder
  • defaultTag
  • groupKeyBuilder
  • operationKeyBuilder
  • routerName

Sound awful lot like the Structure API for SDK operations. I'd suggest looking at the Output section in SDK docs (all the way to Auth), that should give you an idea how much control people can get with those options. The configuration is here and implementation entry point is here.

}),
query: z.optional(z.never()),
headers: z.optional(z.object({
'X-Request-Id': z.optional(z.string())
Copy link

Choose a reason for hiding this comment

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

for better compatiblity, header should be lowercase

Copy link
Member

Choose a reason for hiding this comment

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

Can you share any details about which services might be incompatible with this casing? I would've actually defaulted to X-Request-ID based on what I see elsewhere https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers

Copy link

Choose a reason for hiding this comment

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

Node.js HTTP servers normalize header keys to lowercase. This isn't an issue when the contract is only used with the fetch adapter, but it could be problematic if users use it with the oRPC Node adapter server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants