-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a rule about send
metaprogramming.
#461
Conversation
@@ -3616,6 +3616,9 @@ resource cleanup when possible. | |||
* <a name="prefer-public-send"></a> | |||
Prefer `public_send` over `send` so as not to circumvent `private`/`protected` visibility. | |||
<sup>[[link](#prefer-public-send)]</sup> | |||
* <a name="prefer-__send__"></a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a blank line before the anchor.
And I guess you'll submit one more PR about |
@bbatsov Isn't the existing rule about I have to think about good (and meaningful) code examples that prove the rules. |
Sorry about this. Was a bit distracted when I made my comment. Just remove the |
@syndbg ping :-) |
Submitted as requested in rubocop/rubocop#2081
@bbatsov Sorry for the delays. Added code examples. Turned out that thinking of good examples for trivial stuff is hard. 🎱 |
@bbatsov ping. |
Add a rule about `send` metaprogramming
👍 |
Add a rule about `send` metaprogramming
Submitted as requested in rubocop/rubocop#2081