-
-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(core): add render preset #239
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@Gomah is attempting to deploy a commit to the t3-oss Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Sorry for not seeing this sooner
export const render = () => | ||
createEnv({ | ||
server: { | ||
IS_PULL_REQUEST: z.string().optional(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something to think of for the future, should we coerce booleans like this? Similar for process.env.VERCEL
which is either 1 or 0
z.coerce.boolean()
?
ref: https://docs.render.com/environment-variables#all-runtimes