-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Add a way to initializate debug extension before every new debug session #81806
Comments
@TylerLeonhardt yes this is by design. So as a workaround your extension can just make some edit to the underlying |
Does the
yeah this is exactly what I'm looking for. |
We can change the title of this issue to maybe "Add a mechanism to allow for initialization before every new debug session"? |
Yes, I have renamed it. And it is a fair feature request |
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
I find it unlikely that this will gain enough traction considering it's only an ask from the extension development side. I'd would love to see more discussion from the VS Code team side on this as it would still be nice to have available for extension authors. |
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation. Happy Coding |
Pls no |
Sorry I don't understand the use-case, why do you need this? If there is some setup to run when the debug adapter starts, then wouldn't the debug adapter code itself do that? |
Basically there is code inside of |
That should be in a |
Yeah I tried the powershell extension today and it seems to be working so I think the scenario is covered. |
Version: 1.39.0-insider
Commit: b0d714d
Date: 2019-09-26T09:05:41.420Z
Electron: 6.0.9
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Darwin x64 18.7.0
Steps to Reproduce:
You'll notice nothing happens... this is because
resolveDebugConfiguration
is not run for when the debug adapter is starting up again so it can't set up needed state on the client side.The 'restart' command isn't supported so this is behavior should be shutting down and starting up the debug adapter again.
Is this by design that it's not running
resolveDebugConfiguration
on restart? If so, any recs on how we can set up state in the extension host side before the debug adapter is launched?The text was updated successfully, but these errors were encountered: