Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for multi-line .env files #22411

Closed
CedricVandelaer opened this issue Nov 2, 2023 · 2 comments
Closed

Support for multi-line .env files #22411

CedricVandelaer opened this issue Nov 2, 2023 · 2 comments
Assignees
Labels
area-environments Features relating to handling interpreter environments feature-request Request for new features or functionality

Comments

@CedricVandelaer
Copy link

In several projects I encounter environment variables that span several lines. This is not a problem for Docker or other software, but VS Code currently does not support .env variables across multiple lines.

So for example:
MY_ENV_VAR='{
"key": "value"
}'

Is not supported. This is quite annoying for development.

@CedricVandelaer CedricVandelaer added the feature-request Request for new features or functionality label Nov 2, 2023
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Nov 2, 2023
@karthiknadig karthiknadig added needs community feedback Awaiting community feedback and removed triage-needed Needs assignment to the proper sub-team labels Nov 2, 2023
Copy link

github-actions bot commented Nov 2, 2023

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

@karthiknadig karthiknadig added the area-environments Features relating to handling interpreter environments label Nov 2, 2023
@karrtikr
Copy link

karrtikr commented Nov 2, 2023

We plan to use the official dotenv syntax long term #20003, and given it supports this scenario it should be addressed with it. Closing in favor of #20003.

@karrtikr karrtikr closed this as not planned Won't fix, can't repro, duplicate, stale Nov 2, 2023
@github-actions github-actions bot removed the needs community feedback Awaiting community feedback label Nov 2, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-environments Features relating to handling interpreter environments feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants