Respect Ruby semantics for bare visibility with singleton defs #1632
+72
−34
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.
Description
YARD incorrectly marked singleton method definitions (
def self.x) as private when a bare private appeared earlier in the class body. This problem was originally described here (#1496). Ruby semantics say a bare access modifier affects only the current def-target:class << self: affects class methods onlydef self.xin a class body remains public unless:private_class_methodis used, orprivateappears insideclass << selfThis PR brings YARD in line with Ruby.
Behavior change:
private/public/protectednow only affect methods whose scope matches the current def-target.@!visibilitydirective continues to apply regardless of method scope (as before), since it’s a documentation control.private :foo/public :fooare unaffected.private_class_method/public_class_methodhandlers continue to set exact visibilities.So, the code from the issue now outputs correctly:
Completed Tasks
bundle exec rakelocally (if code is attached to PR).