Empty ENV is removed instead set as empty string in version 2.3

[radeno]

Steps to reproduce

In file .env.development i have these variables:

DATABASE_PASSWORD=
DATABASE_USERNAME=root
DATABASE_HOST=/tmp/mysql.sock

Expected behavior

Variables should be parsed as:

 "DATABASE_PASSWORD"=>"",
 "DATABASE_USERNAME"=>"root"
 "DATABASE_HOST"="/tmp/mysql.sock"

Actual behavior

In 2.3 missing whole keys DATABASE_PASSWORD and also DATABASE_USERNAME because it is next after empty env variable.

Everything OK in 2.2

System configuration

dotenv version: 2.3

Rails version: 5.2

Ruby version: 2.5

[radeno]

Problem is in multiline parser

When i define env vars with new line between them:

DATABASE_PASSWORD=

DATABASE_USERNAME=root

DATABASE_HOST=/tmp/mysql.sock

it is parsed as:

 "DATABASE_HOST"=>"/tmp/mysql.sock",
 "DATABASE_PASSWORD"=>"DATABASE_USERNAME=root"

[jonmagic]

Thank you for the bug report. Looking into potential solutions now.

[jonmagic]

We just shipped version 2.4.0 which removes the Parse multiline values support added in 2.3.0 and fixes the parsing regressions.

[wbotelhos]

@radeno @jonmagic To fix that, I just set an empty value, but it should represent a major release:

DATABASE_PASSWORD=''

[radeno]

@wbotelhos Yes we can pass empy string. But define variable without value is valid. No value as just empty string quotes is very rare.