Expose MethodAlias#target in the Ruby API#796
Merged
Conversation
vinistock
force-pushed
the
05-08-expose_methodalias_target_in_the_ruby_api
branch
from
0043c6d to
ebf60a3
Compare
vinistock
force-pushed
the
05-08-expose_methodalias_target_in_the_ruby_api
branch
from
ebf60a3 to
769f430
Compare
st0012
approved these changes
Jun 11, 2026
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
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.
We need to be able to follow method alias targets in the LSP to concatenate their documentation on hover/completion resolve.
The idea is just exposing
query::follow_method_aliasin the Ruby API, but I also added some custom error classes for a nicer experience in error scenarios.