Skip to content

Use an output channel#327

Merged
JPinkney merged 3 commits intoredhat-developer:masterfrom
apupier:useAnOutputChannel
Jul 24, 2020
Merged

Use an output channel#327
JPinkney merged 3 commits intoredhat-developer:masterfrom
apupier:useAnOutputChannel

Conversation

@apupier
Copy link
Copy Markdown
Member

@apupier apupier commented Jul 23, 2020

for instance, currently with VS Code Kubernetes extension which is throwing error with - file content:
Screenshot from 2020-07-23 10-42-45

requires #324

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
@JPinkney
Copy link
Copy Markdown
Contributor

Is there anyway we can re-use the "YAML Support" output channel instead of creating a new one? The output channel name is automatically taken from: https://github.com/redhat-developer/vscode-yaml/blob/master/src/extension.ts#L60

@apupier
Copy link
Copy Markdown
Member Author

apupier commented Jul 23, 2020

it is possible but it will mix the information coming from the Yaml Language Server and from the extension itself.

@JPinkney
Copy link
Copy Markdown
Contributor

I think that's fine. I think users will be confused when there are two output channels for the same project.

By default yaml.trace.server is "off" anyways so the information from the language server is exposed only when they set yaml.trace.server to messages or verbose

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
@JPinkney JPinkney merged commit e6420dc into redhat-developer:master Jul 24, 2020
bleach31 pushed a commit to bleach31/vscode-yaml that referenced this pull request Jan 25, 2022
Signed-off-by: Yevhen Vydolob <yvydolob@redhat.com>
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.

2 participants