Skip to content
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

private/protected indentation fixes according to rails coding conventions #1838

Closed
wants to merge 1 commit into from

Conversation

luckydev
Copy link
Contributor

I made a few private/protected indentation fixes in ActiveRecord, according to rails coding conventions given here http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#follow-the-coding-conventions

@josevalim
Copy link
Contributor

Thanks for the pull request, but those style changes just break the other pull requests without an explicit gain.

@josevalim josevalim closed this Jun 23, 2011
@luckydev
Copy link
Contributor Author

Should I make those changes in small chunks? I ran the testcases and everything was fine.

@josevalim
Copy link
Contributor

Thanks but there is no need. We are in general denying style changes.

@luckydev
Copy link
Contributor Author

Got it. Thanks

@spastorino
Copy link
Contributor

Also this style changes are wrong. private, protected and public are just method calls so code shouldn't be indented after them.

@luckydev
Copy link
Contributor Author

but the guide lines are asking us to do so.. and I can see them in many rails libs too...

@spastorino
Copy link
Contributor

Yeah ok, the guides are wrong so :), we need to fix that

jake3030 pushed a commit to jake3030/rails that referenced this pull request Jun 28, 2011
…te:resolved]

Signed-off-by: Pratik Naik <pratiknaik@gmail.com>
@retr0h
Copy link
Contributor

retr0h commented Jan 27, 2012

I actually think private/protected should be outdented.

class Foo
  def bar
  end

private
  def baz
  end
end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants