John Barton

I'm sorry, call it a failure of imagination on my part, but what specifically is the use-case here? The scope of this library is to provide developer convenience when implementing...

I would like to support multiline. Do you know if this behaviour is consistent with the ruby & node dotenv libraries?

Sorry for the delay, I'm planning on doing a maintenance pass over all my outstanding GitHub over the Xmas break

I'm doing some manual testing on my end to ensure this change is in line with https://github.com/bkeepers/dotenv/blob/master/spec/dotenv/parser_spec.rb#L198-L234 If so, I'll merge and cut a release.

@x1unix in testing your PR I've found a problem with windows newlines. To give myself extra piece of mind that your multiline behavior matches the canonical ruby implementation I copied...

The change looks good, has tests, seems like it would work. I'm not too keen on merging it without understanding the purpose. Is this an implementation of #38? If so,...

I can't say I've seen that particular error before. I just tried to replicate by modifying some one of the tests for the package to trace the cwd on my...

That one definitely is the expected behaviour, the dotenv file should be found at the execution root. If you're hoping to vary .env based on dev/test, you'll need to manually...

Right. Apparently this is documented behaviour (see https://go-review.googlesource.com/c/go/+/17949) but I was never aware of it. I'll have a think of the best way to document (and/or a recommended work around)...

> While .env in the project root is the default, you don't have to be constrained, both examples below are 100% legit > > _ = godotenv.Load("somerandomfile") > _ =...