Add ability to skip zod's parsing

[KATT]

When using tRPC, it's common to use the same validation schema on the server as the client. Therefore, it's good to be able to send the unparsed raw values from the client to the server.

Maybe this should be the default behavior, unsure if it's intentional to be as it is.

[KATT]

Unsure if it was ever intentional to pass the parsed output here.

[bluebill1049]

Thanks for the PR, it's intentional to return what's provided by the resolvers. What's the issue that brings?

[KATT]

I made a reproduction

1. Go to https://kitchen-sink-git-repro-trpc.vercel.app/react-hook-form
2. Open network tab
3. Fill in form

• Expected: submits successfully
• Actual doesn't work

Highlighted inline here trpc/examples-kitchen-sink#36 on why it doesn't work - it's because the zod resolver coerces the values before sending them to the server which will then try to validate them based on the input:

1. dateStr gets validated as Date on client
2. Date is sent to server
3. Server receives Date, tries to validate as a string --> ❌

[bluebill1049]

thanks for the context. rawValues option I couldn't find in zod's doc do you have a reference?

[KATT]

With raw just means that we're not using zod's parsed output

[KATT]

I had a look around and there's inconsistency how the resolvers behave in terms of this

Here's a few that return the raw value as default:

• resolvers/vest/src/vest.ts

  Line 50 in 350d255

  return { values, errors: {} };

• resolvers/typanion/src/typanion.ts

  Line 37 in 350d255

  return { values, errors: {} };

• resolvers/nope/src/nope.ts

  Line 45 in 350d255

  return { values, errors: {} };

• resolvers/class-validator/src/class-validator.ts

  Line 61 in 350d255

  return { values, errors: {} };

[KATT]

If you want to avoid breaking changes, we can't have a default behavior for this. I think it's better to only add it to zod for now.

[bluebill1049]

great find 👍 let's keep them consistent. ❤️

[KATT]

1. Do you want this to be done ahead of merging this PR?
2. What behavior do you want as default?

[bluebill1049]

The default behavior should return by what returned by the resolver

rawValues: false

and users can opt in to return rawValues if they want the values to return by hook form. I am happy to merge this PR to get started just let @jorisre do a review on this as well.

[KATT]

You see here @bluebill1049, the default behavior is to apply the transforms which will give a Date here and not a string

[bluebill1049]

LGTM

[jorisre]

LGTM ! Thank you for the PR @KATT

[bluebill1049]

@jorisre merge when you feel comfortable ❤️ This should be a minor version and we can follow up to patch the other resolvers as well.

[github-actions]

🎉 This PR is included in version 2.8.9 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀