Add TypeNode#private?, #public? and #visibility
#11696
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
|
Why |
|
Please let's start with an issue to discuss this feature first. |
straight-shoota
approved these changes
Apr 4, 2024
straight-shoota
changed the title
TypeNode#private?TypeNode#private?, #public? and #visibility
1 task
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.
Adds the
TypeNode#private?method to check for the visibility of classes and modules.This is mostly relevant for cases in which a
TypeNodeis directly available (e.g. for iterating and resolving any public elements ofTypeNode#ancestors).Resolves #11705