Don't parse correct for ENV which value is another defined env?

[zw963]

Following ENV not work as expected.

# .env
APP_PORT=3000
APP_NAME=production_line_report
LUCKY_ENV=development
DB_HOST=localhost
DB_PORT=5432
DB_USERNAME=postgres
DB_PASSWORD=postgres
DB_NAME=${APP_NAME}_${LUCKY_ENV}

the expected DB_NAME is product_line_report_development, but the actually is: ${APP_NAME}_${LUCKY_ENV}.

If source ~/.env use bash shell, the result is expected.

So, i consider we should support this, give the user the least surprise

[zw963]

I create a PR for fix this. #31

[jwoertink]

I actually would never expect this to work. I've never seen this sort of interpolation in a .env file before. I do like the change, but I also want to be clear that this shard is not intended to be a bash-like ENV loader. This shard will eventually change #1 to be very specific to Lucky's needs.

But for now, I think this is a nice change and we can add it in 👍