useQuery query options allow unknown key values

[lexer21]

Environment

Node v22.15.0
orpc v1.13.2

Reproduction

NestJS + orpc example: https://github.com/unnoq/orpc/tree/main/playgrounds/nest

Describe the bug

When running the example NestJS repo and trying to use the orpc client with useQuery the input objects accepts any key values. Is this intentional or a bug?

From the provided NestJS example code

// contract/planet.ts
export const listPlanets = oc
  .route({
    method: 'GET',
    path: '/planets',
    summary: 'List all planets',
    tags: ['Planets'],
  })
  .input(
    z.object({
      limit: z.number().int().min(1).max(100).default(10),
      cursor: z.number().int().min(0).default(0),
    }),
  )
  .output(z.array(PlanetSchema))


// playground-tanstack-query.ts
import { orpc } from './lib/orpc'
import { useQuery } from '@tanstack/react-query'
const {data} = useQuery(orpc.planet.list.queryOptions({input: {cursor: 1, limit: 12, test: "123"}}))

In the above code TS compiler does not raise a error Object literal may only specify known properties for key value test: "123" eventhough it is not defined in the contract. However if I use useMutation. In the mutate function, it does raise an error if I provide an unknown key value. Comming from trpc this is very unintuitive for me since there when using useQuery with trpc client i would allways get an error if specifying unknown values for the input.

Additional context

No response

Logs

[dosubot]

This is intentional and not a bug—it's a known limitation of how orpc's TanStack Query integration types the input for useQuery. The queryOptions input is permissive (typed as any), so TypeScript doesn't enforce strict object shapes or flag unknown keys in the input object. This is a trade-off to support all TanStack Query features and allow input to be optional or undefined, not a bug in orpc's type definitions. In contrast, useMutation's input typing is stricter due to how mutation functions are typed and used in the library, which is why you see errors there but not with useQuery.

tRPC enforces stricter input validation at compile time, but orpc's current design for queryOptions does not. There are no built-in safeguards or stricter type checks in recent orpc releases to prevent passing unknown keys in queryOptions. The recommended best practice is to always nest your procedure inputs under the input key and match your contract schema. If you want stricter enforcement, you can add custom linter rules or wrapper utilities in your codebase to catch accidental extra properties in queryOptions input. For more details, see the discussion and maintainer comments here: orpc issue #952.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[unnoq]

This is expected behavior for current oRPC approach, and I hope v2 can improve this.