@snoyberg I think lookupEnvVar would have been a more consistent name, considering that there are functions with names:
modifyEnvVars
withModifyEnvVars
envVarsL
envVarsStringsL.
All of which operate on EnvVars in the ProcessContext, but do not mention it in the name. In fact lookupEnvFromContext will be the first function to have both Context (without Process) and Env (without Var) in its name.
That being said, I really don't care about it, just wanted to express this observation.
As always, let me know if there is anything you'd like me to change./
@snoyberg I think
lookupEnvVarwould have been a more consistent name, considering that there are functions with names:modifyEnvVarswithModifyEnvVarsenvVarsLenvVarsStringsL.All of which operate on
EnvVarsin theProcessContext, but do not mention it in the name. In factlookupEnvFromContextwill be the first function to have bothContext(withoutProcess) andEnv(withoutVar) in its name.That being said, I really don't care about it, just wanted to express this observation.
As always, let me know if there is anything you'd like me to change./