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

Don't autofill values when configuring the debugger for Flask or Django apps #9869

Closed
luabud opened this issue Feb 3, 2020 · 1 comment
Closed
Labels
area-debugging feature-request Request for new features or functionality needs PR Ready to be worked on

Comments

@luabud
Copy link
Member

luabud commented Feb 3, 2020

When debugging Flask and Django applications, the extension tries to detect manage.py and app.py in the application, and if it finds it, it automatically fills its path in the launch.json file, isn't that correct?
When it fails to detect it, it gives the user the option to enter the path to the application, and it prefills with app.py for Flask and manage.py for Django. However, because it is already auto filled, users expect this to be the correct entry and therefore don't change that field. If users have to fill the value in, there are greater chances that they will be successful.

I think microsoft/vscode-python-debugger#161 would be more helpful than this, but we could do both.

@luabud luabud added feature-request Request for new features or functionality triage-needed Needs assignment to the proper sub-team and removed triage-needed Needs assignment to the proper sub-team labels Feb 3, 2020
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Feb 3, 2020
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Feb 3, 2020
@github-actions github-actions bot removed the needs PR label Aug 9, 2022
@karrtikr karrtikr added the needs PR Ready to be worked on label Aug 9, 2022
@paulacamargo25
Copy link

I will close this issue because it will be covered in microsoft/vscode-python-debugger#161.

@paulacamargo25 paulacamargo25 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 21, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 21, 2023
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 needs PR Ready to be worked on
Projects
None yet
Development

No branches or pull requests

3 participants