feat: directly pass zod objects to server and client #272
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@feder240516 is attempting to deploy a commit to the t3-oss Team on Vercel. A member of the Team first needs to authorize it. |
feder240516
force-pushed
the
feat/169-zod-object-directly-passed
branch
from
91935e2 to
6c47d37
Compare
feder240516
force-pushed
the
feat/169-zod-object-directly-passed
branch
from
6c47d37 to
0d51408
Compare
| FOO_BAR: z.string(), | ||
| // @ts-expect-error - no FOO_ prefix |
There was a problem hiding this comment.
hmm having the error on the key is a bit nicer ux
| @@ -16,12 +16,12 @@ function ignoreErrors(cb: () => void) { | |||
| test("server vars should not be prefixed", () => { | |||
| ignoreErrors(() => { | |||
| createEnv({ | |||
| server: { | |||
| // @ts-expect-error - server should not have NEXT_PUBLIC_ prefix | |||
| // @ts-expect-error - server should not have NEXT_PUBLIC_ prefix | |||
| server: {}, | ||
| client: { | ||
| server: z.object({}), | ||
| // @ts-expect-error - no NEXT_PUBLIC_ prefix |
@juliusmarminge it's something that I've explored, but I don't think it's possible, due to the properties being now part of the zod schema constructor |
|
hey we added standard schema support #299 so i think this will need to be restarted / abandoned. i'll close it given the amount of conflicts but the issue is still up |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #169
Improvements:
ZodObjects with transforms / refines / catchs are not supported. The same goes for other specialized types (z.union, z.discriminatedUnion, z.record).Discussion:
ZodObjects are accepted