jaredramirez / elm-constants Goto Github PK

To reproduce:

.env:

BASE_PATH=

elm-constants.json:

{
  "path": "./src/",
  "moduleName": "Env",
  "values": [
    "BASE_PATH"
  ]
}

Run elm-constants.

Expected behavior:

Env.elm produced with basePath = "".

Actual behavior:

I couldn't find any of the environment variable you specified, so I have nothing to generate!

BASE_PATH="" of course does not change anything because it produces the same shell variable with the same shell value.

I guess the issue is here:

There's a confusion here between falsy environment variables and those which are missing.

I think there's also a larger issue here which is that we shouldn't try to be "safe" against missing environment variables. Elm code cannot detect undefined variables, so if a variable is truly missing, we should probably error out immediately rather than let later compilation steps fail when the variable is not there.