[BUG] Debugging with purpose ignored in user/workspace settings.

[byehack]

Environment data

• VS Code version: v1.60.0
• Extension version (available under the Extensions sidebar): v2021.9.1246542782
• OS and version: win10 20h2 64bit
• Python version (& distribution if applicable, e.g. Anaconda): py3.7.7 32bit
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): `N/A
• Relevant/affected Python packages and their versions: pylance v2021.9.4, jupyter v2021.8.2041215044
• Value of the python.languageServer setting: Default

Steps to reproduce:

1. add this configuration in workspace/user settings:

    "launch": {
        "version": "0.2.0",
        "configurations": [
            {
                "name": "Python: Current File - Editor button",
                "type": "python",
                "request": "launch",
                "program": "${file}",
                "console": "integratedTerminal",
                "justMyCode": false,
                "purpose": ["debug-in-terminal"]
            }
        ]
    }

2. try debug from editor button, it doesn't work. but in folder launch.json it works.

Logs

EMPTY

[karthiknadig]

Currently we only check the launch.json file when looking for debug-test and debug-in-terminal

[byehack]

also it would be great something like this for purpose:

"purpose": ["debug-in-terminal",  "debug-test", "debug-normal"]

[byehack]

loose files cannot have configured debug button in python: #525

It would be great to configure run/debug button for loose files:

1. If file is in workspace but there is no launch.json: use Workspace launch settings(if it's set else ask to use LS provided settings or create/set new one. )
2. If file is not in workspace: use launch in user settings (if it's set else ask to use LS provided settings or create/set new one. )

by these cases the priority is launch.json > Workspace > User
If none of them were set, it should show these items in quick input menu:

• use language provided settings
• use and remember language provided settings
• new configuration in user settings
• new configuration in workspace settings
• new configuration in launch.json settings (if file isn't loose)

Originally posted by @byehack in microsoft/vscode#124280 (comment)

[eleanorjboyd]

Hello! I wanted to check in to see if this is still an issue you are facing given it has been a while since you originally filed it. Thanks!

[karthiknadig]

This is still a bug. Essentially, we are not looking at the settings.json for launch configs, we are only picking it up from launch.json.