Skip to content
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

Always try to register for didChangeConfiguration #548

Merged
merged 3 commits into from
Feb 4, 2024

Conversation

michaelpj
Copy link
Collaborator

Still needs some lsp-test work, but I think this should work.

@michaelpj michaelpj force-pushed the mpj/dynamic-did-change-configuration branch from 42c31d3 to c6a9b9b Compare February 3, 2024 18:10
@michaelpj michaelpj marked this pull request as ready for review February 3, 2024 18:10
@michaelpj
Copy link
Collaborator Author

Okay, this is ready to go now, I think.

  • lsp always registers for didChangeConfiguration
  • lsp-test adapts to cope with the increased registerCapability spam
  • lsp-test acts as a more unhelpful client and doesn't send notifications unless we ask for them

@michaelpj
Copy link
Collaborator Author

Going to test this with HLS now.

@michaelpj
Copy link
Collaborator Author

Got things working fine on HLS it seems, just need to get this green.

@michaelpj
Copy link
Collaborator Author

The new direction of the spec seems to be that you should always do
this. In any case, it doesn't hurt.

`lsp-test` has some changes to adapt to the increased registration
message spam, and also changes to be a more picky client, refusing to
send notifications unless you _do_ register. This is good, since it
forces us to handle the most annoying version of client behaviour.
@michaelpj michaelpj force-pushed the mpj/dynamic-did-change-configuration branch from 6e9f082 to 300fdd6 Compare February 4, 2024 17:44
@michaelpj michaelpj merged commit 13cba17 into master Feb 4, 2024
14 checks passed
soulomoon pushed a commit to soulomoon/lsp that referenced this pull request Apr 8, 2024
* Register for workspace/didChangeConfiguration always

The new direction of the spec seems to be that you should always do
this. In any case, it doesn't hurt.

`lsp-test` has some changes to adapt to the increased registration
message spam, and also changes to be a more picky client, refusing to
send notifications unless you _do_ register. This is good, since it
forces us to handle the most annoying version of client behaviour.

* Add bound on extra

* fix
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.

1 participant