bug: Query with optional `any` input still needs to be passed an input value about trpc HOT 4 CLOSED

Not sure if we wanna fix this due to the complexity it entails and that we'll need to fix stuff in downstream libraries (@tanstack/query), you can pass in undefined which is effectively the same thing and any is an edge case [that should be avoided] -

from trpc.

I have "fixed" it in #5774 but unsure if I should merge it

Current behavior matches the behavior of TypeScript

Example:

function fn(input: any) {}


fn() // <-- ❌

from trpc.

Yeah, we won't fix this in tRPC - it adds a lot of maintenance burden for something that works the way TypeScript works.

If you want to fix this, file/find an issue in TypeScript that should allow type T = any | undefined to be anything else but any

from trpc.

This issue has been locked because we are very unlikely to see comments on closed issues. If you are running into a similar issue, please create a new issue. Thank you.

from trpc.