-
Notifications
You must be signed in to change notification settings - Fork 490
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
Support VS Code 'Set Log Level' #4441
Comments
Thanks for the Issue Submit! So this is a fairly new API that logging has to be explicitly written for: The PowerShell extension has its own logger implementation and would need to be updated for this new API. And then wired up so that |
Thanks for taking a look at it. For reference, here is that logging line without Visual Studio Code for the Web. vscode-powershell/src/logging.ts Line 49 in 019a9f8
|
Problem: `vscode.LogOutputChannel` loglevel is currently readonly: - microsoft/vscode#170450 - PowerShell/vscode-powershell#4441 So `debug()` will just drop messages unless the user has increased vscode's log-level. Solution: Write "debug" logs using `info()` until vscode adds a way to set the loglevel.
Problem: `vscode.LogOutputChannel` loglevel is currently readonly: - microsoft/vscode#170450 - PowerShell/vscode-powershell#4441 So `debug()` will just drop messages unless the user has increased vscode's log-level. Solution: Write "debug" logs using `info()` until vscode adds a way to set the loglevel.
Working on this in #5065 but there's some upstream vscode bugs I need addressed. |
Prerequisites
Summary
VS Code version 1.76 has a "Developer: Set Log Level..." command. I tried using the command while I had a PowerShell project loaded. But I did not see an explicit option for the PowerShell extension. I'm not sure if the extension outputs to a generic log or if the PowerShell extension should be represented on this list.
'Set Log Level' seems like a useful command. Please take a look at it and see if the PowerShell extension can support this VS Code command.
References
Proposed Design
No response
The text was updated successfully, but these errors were encountered: