Bugs in parser around unquoted whitespace and newlines in v1.5.0

[andreynering]

Hi there!

I'd just like to let you know that the following, which worked on v1.4.0, now breaks in v1.5.0:

MY_ENV=foo bar

It's possible to fix by wrapping into quotes, though:

MY_ENV="foo bar"

As there isn't any official dotenv specification (AFAIK), I'm not sure if the former is supposed to work in the first place, but it caught my attention and I decided to wait until at least we have a decision if this is going to be addressed or not before upgrading, because it can end up breaking for my users.

[joho]

It's definitely unintended, in that it wasn't an explicit decision, though I'd say it was "undefined" behaviour.

I'll go check what ruby/node do, and we'll do the same as them.

[joho]

Yep, so I've gone and tested against ruby. This is a regression, will fix and get a 1.5.1 out

[joho]

Yeah I did a pretty ordinary job code reviewing the multiline PR and it's pulled a few regressions in, some in previously "undefined" behaviour, and some in tests that weren't updated to exercise the newer code paths.

Fix might be this week, might drag out a bit, got a hectic schedule at the moment.

[budimanjojo]

I'm wondering if my issue is the same, because I'm using yaml format for the test, and most people don't put " for yaml value. This test string:

env1: value1
env2: "true"
env3: 123
default: default value

using godotenv.Unmarshal(testFile)
resulted in nothing is being set at all.

    envsubst_test.go:59: got , want value1       
    envsubst_test.go:59: got , want true         
    envsubst_test.go:59: got , want 123          
    envsubst_test.go:59: got , want default value

[joho]

Yeah, I suspect it's the exact same issue. I'll put in a test case on my branch that covers that in yaml style explicitly.

[joho]

Yep, definitely is, here's some test output from my new cases

--- FAIL: TestTrailingNewlines (0.00s)
    --- FAIL: TestTrailingNewlines/Value_with_internal_whitespace_with_trailing_newline (0.00s)
        godotenv_test.go:566: Input: "KEY=value value\n" Unexpected error:	"unexpected character \"\\n\" in variable name near \"value\\n\""
        godotenv_test.go:569: Input "KEY=value value\n" Expected:	 "KEY"/"value value"
            Got:	 map["KEY":"value"]
    --- FAIL: TestTrailingNewlines/YAML_style_-_value_with_internal_whitespace_without_trailing_newline (0.00s)
        godotenv_test.go:569: Input "KEY: value value" Expected:	 "KEY"/"value value"
            Got:	 map["":"value" "KEY":"value"]
    --- FAIL: TestTrailingNewlines/YAML_style_-_value_with_internal_whitespace_with_trailing_newline (0.00s)
        godotenv_test.go:566: Input: "KEY: value value\n" Unexpected error:	"unexpected character \"\\n\" in variable name near \"value\\n\""
        godotenv_test.go:569: Input "KEY: value value\n" Expected:	 "KEY"/"value value"
            Got:	 map["KEY":"value"]
    --- FAIL: TestTrailingNewlines/Value_with_internal_whitespace_without_trailing_newline (0.00s)
        godotenv_test.go:569: Input "KEY=value value" Expected:	 "KEY"/"value value"
            Got:	 map["":"value" "KEY":"value"]

[budimanjojo]

I think it's this line:

godotenv/parser.go

Lines 115 to 123 in b311b26

	if !hasPrefix {
	// unquoted value - read until whitespace
	end := bytes.IndexFunc(src, unicode.IsSpace)
	if end == -1 {
	return expandVariables(string(src), vars), nil, nil
	}
	return expandVariables(string(src[0:end]), vars), src[end:], nil
	}

Not sure what will happen if we just remove that check, is there a usecase where unquoted value can't have space? I think for both .yaml and .env format we only need to quote for "newline(\n)" and not " "?