-
Notifications
You must be signed in to change notification settings - Fork 29.3k
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 to provide task definitions through DebugConfiguration.preLaunchTask #78948
Comments
(Experimental duplicate detection) |
Not a duplicate. |
A |
No, because my understanding was that the preLaunchtask is launched before the session starts and that onDidStartDebugSession is called after. My goal is to create a task to be used as a prelaunchTask. Am I missing something? @weinand |
This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider. If you wonder what we are up to, please see our roadmap and issue reporting guidelines. Thanks for your understanding and happy coding! |
Hello @g-arjones, did you manage to do this? I want to do the same thing now and I am stuck. I want to define a preLaunchTask without having to write a tasks.json file, and would like the extension I write to register this automatically. I am not sure whether this is possible. Any insights? |
@weinand Could you please elaborate on this, if you have the time? I am trying to start a debugging session by first running a I would like to abstract this away from the users of my extension so they do not have to define a task for it in the The solutions I have researched so far are:
Later edit: I know this is not a good place to ask questions, but I have already tried my luck on SO, to no avail. |
This is a follow-up from: #59337
The goal is to provide a simple mechanism for a
DebugConfigurationProvider
to create task definitions and use them as prelaunch tasks. ATaskProvider
would then be able to pick those up and fill the missing bits. Currently, there is no way to gather data from debugging configurations provided by the user through launch.json and pass it to a task provider so that prelaunch tasks could be created dynamically off the debug configuration.I will be glad to hear workarounds as well..
The text was updated successfully, but these errors were encountered: