How to deal with env variable being string | undefined when clientId is expecting only string?

I'm trying to think of a solution to this... any ideas? So far I'm just doing typeof, and if it is not string then error.

Samathingamajig•11/20/22, 6:44 AM

Are you using zod to parse your env file, like we use in create-t3-app?

Samathingamajig•11/20/22, 6:44 AM

if you are, make sure that you import instead of going off of

nexxel•11/20/22, 6:46 AM

people usually do

nexxel•11/20/22, 6:46 AM

but its better to validate using zod

nexxel•11/20/22, 6:46 AM

we have a very nice system in create-t3-app

amanuelOP•11/20/22, 6:47 AM

No I don't like type assertion here

amanuelOP•11/20/22, 6:47 AM

ok, I'll try using zod

amanuelOP•11/20/22, 6:48 AM

Yeah I already created my own system, t3-stack scaffold wasn't ready yet

amanuelOP•11/20/22, 6:48 AM

@nexxel Any documentation on this zod?

nexxel•11/20/22, 6:48 AM

a simpler way to validate would be like this

nexxel•11/20/22, 6:48 AM

nexxel•11/20/22, 6:48 AM

now import env from here and everything will autocompleted and typesafe

nexxel•11/20/22, 6:49 AM

and it will throw an error if it doesn't match this schema

amanuelOP•11/20/22, 6:50 AM

this is literally god mode

amanuelOP•11/20/22, 6:50 AM

they should call it "god" instead of "zod"

amanuelOP•11/20/22, 6:50 AM

Thanks for this suggestion

Scot•11/20/22, 7:04 AM

I mean what do you want to do if it's not defined?

Scot•11/20/22, 7:04 AM

You could just throw yourself

Scot•11/20/22, 7:04 AM

Or set it to a default

amanuelOP•11/20/22, 7:15 AM

yeah, that's what I was doing