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

Allow multiple .env files in envFile for debugging #10142

Closed
jordangarside opened this issue Feb 14, 2020 · 2 comments
Closed

Allow multiple .env files in envFile for debugging #10142

jordangarside opened this issue Feb 14, 2020 · 2 comments
Labels
area-debugging feature-request Request for new features or functionality

Comments

@jordangarside
Copy link

jordangarside commented Feb 14, 2020

Hi there,

Would it be possible to get support for multiple env files when debugging?

// launch.json
{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Python",
      "type": "python",
      "request": "launch",
      "program": "app.py",
      "console": "integratedTerminal",
      "envFile": [
        "${workspaceFolder}/config/environment/base.env",
        "${workspaceFolder}/config/environment/development.env"
      ]
    }
  ]
}

It looks like this was added to vscode-go:
Issue: microsoft/vscode-go#1746
PR: microsoft/vscode-go#2395

Thanks!

@jordangarside jordangarside added triage-needed Needs assignment to the proper sub-team feature-request Request for new features or functionality labels Feb 14, 2020
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Feb 18, 2020
@karthiknadig
Copy link
Member

Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.

@luabud
Copy link
Member

luabud commented Mar 25, 2020

Thanks for the suggestion! We talked about it with the team and we have unfortunately decided we will not be moving forward with this idea. We think there isn't an enough widespread need for this to warrant the maintenance cost for the feature.

@luabud luabud closed this as completed Mar 25, 2020
@ghost ghost removed the needs decision label Mar 25, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Apr 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants