Skip to content

Handle visibility in go to definition#4095

Merged
vinistock merged 1 commit intorubydex_adoption_feature_branchfrom
vs_handle_visibility_in_definition
May 8, 2026
Merged

Handle visibility in go to definition#4095
vinistock merged 1 commit intorubydex_adoption_feature_branchfrom
vs_handle_visibility_in_definition

Conversation

@vinistock
Copy link
Copy Markdown
Member

Motivation

Now that Rubydex exposes the visibility API, we can handle it correctly in go to definition.

Implementation

Added a helper to check if a method is reachable from the current lexical scope and self type, so that we can handle protected methods correctly.

Automated Tests

Added some new tests.

@vinistock vinistock self-assigned this May 7, 2026
@vinistock vinistock requested a review from a team as a code owner May 7, 2026 22:35
@vinistock vinistock added server This pull request should be included in the server gem's release notes other Changes that aren't bugfixes, enhancements or breaking changes labels May 7, 2026
@vinistock vinistock requested review from Morriar, alexcrocha and st0012 May 7, 2026 22:35
@vinistock vinistock mentioned this pull request May 7, 2026
19 tasks
@vinistock vinistock force-pushed the vs_handle_visibility_in_definition branch from 303127b to 8d34acd Compare May 8, 2026 13:59
@vinistock vinistock merged commit b2a6eff into rubydex_adoption_feature_branch May 8, 2026
35 of 36 checks passed
@vinistock vinistock deleted the vs_handle_visibility_in_definition branch May 8, 2026 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

other Changes that aren't bugfixes, enhancements or breaking changes server This pull request should be included in the server gem's release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants