Use YARP-based ruby-lsp #157
Merged
Conversation
This file contains hidden or 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
st0012
force-pushed
the
migrate-to-yarp
branch
2 times, most recently
from
f1988a6 to
3272c1d
Compare
st0012
force-pushed
the
migrate-to-yarp
branch
from
3272c1d to
6c8ac75
Compare
vinistock
approved these changes
Oct 4, 2023
st0012
force-pushed
the
migrate-to-yarp
branch
from
6c8ac75 to
8320daa
Compare
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changes:
ruby-lspand change node types and namespaces...etc.[Ee]xtensionto[Aa]ddonso we can pass type-checking and tests.ruby-lsp. So I updated them all to use source-based approach and extracted boilerplate code into helpers.