Mot
I see. Thanks @hbriese. @rymbekov can you elaborate further? Why do you currently prefer to have multiple .envs for a docker compose container? Do you boot up the docker compose...
There is not yet, but we are going to add it.
> Also what would be the alternative? Just not supporting development on Windows anymore doesn't sound like a good option. You can use `dotenvx` for this in place of `cross-env`....
That is necessary to support the styling. It uses textMateRules - which vscode is based on originally.
unfortunately, so far, this appears to be a vscode limitation. i haven't been able to find a way around it. anyone have any ideas?
Interesting. @akulmehta, can you share an example .yaml file like that?
What frameworks or languages use this .yaml approach? I'm just curious before we start work on this. Why not just use a .env file?
I see. You're using environment variables inside a docker yaml definition file. Optionally, you could reference a .env file from there instead. We recommend this because it is safer and...
That is currently by design - to only look at a `.env` file. Code is here: https://github.com/dotenv-org/dotenv-vscode/blob/master/lib/helpers.js#L17 Reasoning is we've always recommended against having multiple .env files for development, BUT...
Ok, we'll try and get this added as a feature soon - probably configurable in settings.