Styleguide for Rails Projects 1

Geschrieben von Jens am 11. April 2008

Principles

DRY - Don’t Repeat yourself.
http://www.jensjaeger.com/2008/04/das-dry-prinzip/ (german)
http://en.wikipedia.org/wiki/DRY

KISS - Keep it Simple Stupid
http://www.jensjaeger.com/2008/04/das-kiss-prinzip/ (german)
http://en.wikipedia.org/wiki/KISS_principle

General

General Ruby Styleguide
http://rubygarden.org/ruby/page/show/RubyStyleGuide

General Rails Styleguide:
http://wiki.rubyonrails.org/rails/pages/CodingStandards

Language

Everything in the source code must be written in english. Including comments, variable names and function names.

Encoding

All files must be encoded with UTF-8.

Methods

Every method should have a meaningful name.
For a procedure name use a strong verb.
Example:

  1. Report.print

 

For a function name use a description of the return value
Example:

  1. Report.publishing_date

 

Avoid meaningless or wishy-washy verbs.
Descripe everything the method does.
Make names of routines as long as necessary.
The average length of methods should be from 15 to 20 characters.

Variables

Every variable should have a meaningful name.
The most consideration in naming is that the name fully and accurately descripe the entity the variable represents.
The average length of a variable should be from 8 to 15 characters.
Use shorter name only for iterators in really short scopes.
Example:

  1. reports.each do |r|
  2.   r.print
  3. end

 

The scope of a variable should be as short as possible.
Arrays should have a plural name.
Example:

  1. reports = Report.find(:all)

 

Everything else should have a singular name.
Example:

  1. report = Report.find_by_id(1)

Constants

Naming like variables.
There should be no numbers in the sourcecode. Every number should be a constant defined in environment.rb.
Example:

  1. PAG_PAGES = 10 #items per page for pagination

Comments

Comment as much as possible.
You shouldn’t comment WHAT your code does (this would be hurt the DRY-Principle), you should comment WHY your code does something.

Stay DRY

If you are doing something more than once, extract it into a method. This is especially the case when it comes to conditional queries. So instead of writing:

  1. @reports = Report.find(:all, :conditions => ["deleted = ", 1])

you should write a method:

  1. class Report < AR::B
  2.   def find_deleted
  3.     find(:all, :conditions => ["deleted = ", 1])
  4.   end
  5. end

Paranthesis

Use paranthesis with “standard” method calls and no paranthesis for helper-style hash arguments. Example:

  1. Report.find_by_id(1)
  2. #instead of
  3. Report.find_by_id 1

but

  1. ink_to "view", { :action =>; "view" }
  2. #instead of
  3. link_to("view", { :action => "view" })

Acknowledgments

Thanks to Florian Gilcher for the helpful comments.

Trackbacks

Benutze diesen Link um diesen Artikel zu verlinken.

Kommentare

Schreibe einen Kommentar

  1. Extreme Programming - jensjaeger.com Fr, 25 Apr 2008 12:37:15 CEST

    [...] Programmierstandards - Programmierer schreiben sämtlichen Code entsprechend Regeln, die die Kommunikation mithilfe des Codes erleichtern. [...]

Kommentare