Skip to content

Rework log builder to support logging to files #1066

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

Merged
merged 2 commits into from
Oct 15, 2019

Conversation

TylerLeonhardt
Copy link
Member

@TylerLeonhardt TylerLeonhardt commented Oct 14, 2019

the title says it all... 3 cheers for the .NET builder pattern.

Here's what our logs look like.
EditorServices.log

Note, we still need this issue to be resolved to get logs of the payload... but we can get the payloads... just not in the file logs... the user can add:

"powershell editor services.trace.server":"verbose"

in their settings which will give them an Output window in vscode that contains the payloads that is compliant with the lsp inspector.

It's an extra process.. but it's the best we've got so far. It will get better.

Note this also updates the usings for Mediatr due to an Omnisharp change.

@SydneyhSmith
Copy link
Collaborator

SydneyhSmith commented Oct 14, 2019

Looks great--when we merge this change in let's also make sure that we make any necessary changes to our troubleshooting guide and our issue templates

@rjmholt
Copy link
Contributor

rjmholt commented Oct 15, 2019

Merged to get PowerShell/vscode-powershell#2238 building

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants