-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
Adapt to lsp changes for workspace/configuration #3773
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelpj
force-pushed
the
mpj/configuration
branch
from
August 23, 2023 15:10
667a3c8
to
502b312
Compare
Stack builds will fail since I haven't put the git dep in there. Shouldn't be a problem once we're using a released |
It looks like you are just going to satisfy the lsp changes, LGTM. |
michaelpj
requested review from
joyfulmantis,
ozkutuk,
Ailrun,
konn,
kokobd,
pepeiborra,
santiweight,
OliverMadine,
eddiemundo,
berberman,
georgefst,
July541,
VeryMilkyJoe,
fendor and
drsooch
as code owners
August 24, 2023 14:23
michaelpj
force-pushed
the
mpj/configuration
branch
from
August 24, 2023 16:33
a2613c6
to
236e790
Compare
This has a few substantive changes and a lot of messing with tests. - We now tell `lsp` our config section, and parse just that section. - We move the logic for updating the shake build rules for client config from a `workspace/didChangeConfiguration` handler to the new `lsp` callback, which will ensure it gets called in all circumstances that can be relevant. The test changes are more annoying: - We ignore config and logging messages by default now, so we have to stop doing that when we care about it. - Many tests didn't really need to _change_ the config, but rather just to set it once at the beginning. I adjusted a lot of test functions to allow passing in the initial config for this reason.
michaelpj
force-pushed
the
mpj/configuration
branch
from
August 25, 2023 08:45
41d8222
to
50796ed
Compare
fendor
approved these changes
Aug 25, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DRAFT: depends on unreleased
lsp
code, I expect I still messed some stuff up with the testsThis has a few substantive changes and a lot of messing with tests.
lsp
our config section, and parse just that section.workspace/didChangeConfiguration
handler to the newlsp
callback, which will ensure it gets called in all circumstances that can be relevant.The test changes are more annoying: