Skip to content
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

Feature/validate env var #326

Merged
merged 76 commits into from
Apr 18, 2024
Merged

Feature/validate env var #326

merged 76 commits into from
Apr 18, 2024

Conversation

mwskwong
Copy link
Owner

@mwskwong mwskwong commented Apr 8, 2024

closes #322

Caveat

  • Zod is bundled to the client-side
  • No options for using Valibot yet

Prefer to wait for t3-oss/t3-env#6 to resolve before merging

Copy link

vercel bot commented Apr 8, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
mwskwong-com ✅ Ready (Inspect) Visit Preview Apr 18, 2024 9:25am

@mwskwong mwskwong marked this pull request as ready for review April 9, 2024 03:52
Matthew Kwong and others added 3 commits April 18, 2024 16:25
@mwskwong mwskwong marked this pull request as ready for review April 18, 2024 09:30
@mwskwong
Copy link
Owner Author

Decided to just replace Valibot with Zod for now. The mentioned issue has been opened for a year and no sign of
concrete ETA/commitment (it sounds like more of a nice to have to the team).

I will switch back to Valibot once T3 Env supports it.

@mwskwong mwskwong merged commit dac9f6f into canary Apr 18, 2024
7 checks passed
@mwskwong mwskwong deleted the feature/validate-env-var branch April 18, 2024 09:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant