Skip to content

Hls status and cradle-info on VScode#4931

Open
vidit-od wants to merge 3 commits intohaskell:masterfrom
vidit-od:Cradle-Info
Open

Hls status and cradle-info on VScode#4931
vidit-od wants to merge 3 commits intohaskell:masterfrom
vidit-od:Cradle-Info

Conversation

@vidit-od
Copy link
Copy Markdown
Collaborator

@vidit-od vidit-od commented May 8, 2026

Provide support for a PR from Vscode-haskell (link)

This is an attempt to improve user experience by making HLS status more expressive.

logic :

flowchart (1)

vidit-od added 3 commits May 8, 2026 12:20
Sends Cradle Info to vsCode extension. Mechanism to populate status bar items
@vidit-od vidit-od requested review from fendor and wz1000 as code owners May 8, 2026 07:14
@vidit-od vidit-od changed the title Cradle info Hls status and cradle-info on VScode May 8, 2026
@dschrempf
Copy link
Copy Markdown
Collaborator

When you say "VSCode", do you mean LSP-client? Just asking on behalf of the little crew that uses different editors. And thanks for working on the status messages!

@fendor
Copy link
Copy Markdown
Collaborator

fendor commented May 8, 2026

@dschrempf The feature uses a lsp notification that the client can pick up to show the current status.

This requires extra logic in the client, since how you display this notification depends on the client capabilities...
I don't think there is any way in lsp show the status of the server in a generic way, so while the method itself is not VSCode specific, this PR would only be visible with a change in the client.

@dschrempf
Copy link
Copy Markdown
Collaborator

I see. And is there no protocol-conform way to signal status? Seems weird to me that we tailor HLS to an editor when the LSP is supposed to be an editor-agnostic communication protocol.

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