[regression] Fix resolution of a nested type case #1103
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
YARD-parsed namespaces weren't correctly setting their gates, leading to unresolved types from methods.
1) Prefer closures with more gates, to maximize compatibility 2) Look at basename of location, to make choice consistent
Found in the Solargraph::Pin::DelegatedMethod class in strong typechecking in #12
…another_ambiguous_type
…nother_ambiguous_type
…nother_ambiguous_type
This was referenced Oct 1, 2025
…-specs' into fix_resolution_of_another_ambiguous_type
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.
Found in the Solargraph::Pin::DelegatedMethod class in strong typechecking in apiology#12
Includes for safety: