Skip to content

VsCode: create local output channel even if tracing is disabled #5368

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 1 commit into from
Nov 22, 2018

Conversation

abgruszecki
Copy link
Contributor

We should still create a local output channel if remote tracing is disabled, BUT dotty.trace.server is set to be consistent with how other plugins implement the functionality.

I broke the check at the beginning of initializeAsyncWorkspaceDump when I set the default value of workspace dump URL to empty string in package.json. Note that checking if the url is falsey is morally fine, since all falsey strings are invalid (absolute) URLs. This is already done by isTracingEnabled.

Remember to actually check if zip URL is set before zipping.
Checking if url is undefined was meaningless, since it now defaults
to empty string (in package.json).
@abgruszecki abgruszecki requested a review from Duhemm November 2, 2018 08:11
@abgruszecki abgruszecki changed the title VsCode: create local output channel if tracing is disabled VsCode: create local output channel even if tracing is disabled Nov 2, 2018
@smarter
Copy link
Member

smarter commented Nov 5, 2018

We should still create a local output channel if remote tracing is disabled, BUT dotty.trace.server is set to be consistent with how other plugins implement the functionality.

Hmm, so using current master I've tried creating a new project with just:

{
  "dotty": {
    "trace": {
      "server": { "format": "JSON", "verbosity": "verbose" }
    }
  }
}

And I do see lsp logs in "Dotty LSP Communication" in the Output panel.

@abgruszecki
Copy link
Contributor Author

abgruszecki commented Nov 6, 2018

@smarter I just checked and the channel created is named "Dotty", not "Dotty LSP Communication" - seems like VsCode creates a channel for LSP logging automatically if we don't do it ourselves. It does not seem to me like this is the kind of behaviour we want to rely on - it'd be better to consistently use the channel we created and control ourselves.

@smarter
Copy link
Member

smarter commented Nov 13, 2018

Sure.

@abgruszecki abgruszecki merged commit 145cf52 into scala:master Nov 22, 2018
@abgruszecki abgruszecki deleted the local-output-channel branch November 22, 2018 11:30
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