You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's confusing that we are saying "Use the env object" without letting people know that they need to implement validations for each env vars they want to have available on the env object.
We mention user env validation under the title "Custom Env Var Validations" which reads like "something extra to do" and not "you need to define validations for your env vars if you want to use the env object".
We should make it extra clear that that's what's required if you want to use the env object from wasp/server or wasp/client for your env vars. Also, we should make it obvious that the platform primitives of process.env and import.meta.env are still functional if they don't want to validate their env vars.
The text was updated successfully, but these errors were encountered:
Based on this series of messages: https://ptb.discord.com/channels/686873244791210014/812664118887841813/1341866176766017587
It's confusing that we are saying "Use the
env
object" without letting people know that they need to implement validations for each env vars they want to have available on theenv
object.We mention user env validation under the title "Custom Env Var Validations" which reads like "something extra to do" and not "you need to define validations for your env vars if you want to use the
env
object".We should make it extra clear that that's what's required if you want to use the
env
object fromwasp/server
orwasp/client
for your env vars. Also, we should make it obvious that the platform primitives ofprocess.env
andimport.meta.env
are still functional if they don't want to validate their env vars.The text was updated successfully, but these errors were encountered: