re: External dependencies which read and act on environment variables? VIEW POST


First of all, every behavior of a library one is releasing to the public should be documented; failing that simple requirement, I would say your dependency was unfit for public distribution.

Also, environment variables are pretty common in most projects, so one has to be careful to avoid naming conflicts. It should be best practice to have a namespace for your environment variables, e.g. if your project is called foo, prefix them with FOO_NAME instead of just going with NAME.

Code of Conduct Report abuse