mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
Disagree with @spastorino, @jonleighton, @tenderlove on 51ccb7f59c
Same-level method visibility disappears into the syntax. Indent (and outdent) emphasize the state change that accompanies the declaration. All methods following 'private' are private: that's a natural hierarchy worthy of visual reinforcement. Outdent, represent! :trollface:
This commit is contained in:
parent
f1baf8f5a4
commit
faaf694e0f
1 changed files with 1 additions and 1 deletions
|
@ -309,7 +309,7 @@ Rails follows a simple set of coding style conventions.
|
|||
|
||||
* Two spaces, no tabs.
|
||||
* No trailing whitespace. Blank lines should not have any space.
|
||||
* Do not indent after private/protected. Private/protected should have the same indentation as the methods around.
|
||||
* Outdent private/protected from method definitions. Same indentation as the class/module.
|
||||
* Prefer +&&+/+||+ over +and+/+or+.
|
||||
* Prefer class << self block over self.method for class methods.
|
||||
* +MyClass.my_method(my_arg)+ not +my_method( my_arg )+ or +my_method my_arg+.
|
||||
|
|
Loading…
Reference in a new issue