mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
Copy editing to improve readability, consistency, and tone
This commit is contained in:
parent
5f632a88a6
commit
11b183eb92
1 changed files with 4 additions and 4 deletions
|
@ -576,7 +576,7 @@ The <tt>create_<em>association</em></tt> method returns a new object of the asso
|
|||
|
||||
h5. Options for +belongs_to+
|
||||
|
||||
In many situations, you can use the default behavior of +belongs_to+ without any customization. But despite Rails' emphasis of convention over configuration, you can alter that behavior in a number of ways. This section covers the options that you can pass when you create a +belongs_to+ association. For example, an association with several options might look like this:
|
||||
While Rails uses intelligent defaults that will work well in most situations, there may be times when you want to customize the behavior of the +belongs_to+ association reference. Such customizations can easily be accomplished by passing options when you create the association. For example, this assocation uses two such options:
|
||||
|
||||
<ruby>
|
||||
class Order < ActiveRecord::Base
|
||||
|
@ -842,7 +842,7 @@ The <tt>create_<em>association</em></tt> method returns a new object of the asso
|
|||
|
||||
h5. Options for +has_one+
|
||||
|
||||
In many situations, you can use the default behavior of +has_one+ without any customization. But despite Rails' emphasis of convention over configuration, you can alter that behavior in a number of ways. This section covers the options that you can pass when you create a +has_one+ association. For example, an association with several options might look like this:
|
||||
While Rails uses intelligent defaults that will work well in most situations, there may be times when you want to customize the behavior of the +has_one+ association reference. Such customizations can easily be accomplished by passing options when you create the association. For example, this assocation uses two such options:
|
||||
|
||||
<ruby>
|
||||
class Supplier < ActiveRecord::Base
|
||||
|
@ -1156,7 +1156,7 @@ The <tt><em>collection</em>.create</tt> method returns a new object of the assoc
|
|||
|
||||
h5. Options for +has_many+
|
||||
|
||||
In many situations, you can use the default behavior for +has_many+ without any customization. But you can alter that behavior in a number of ways. This section covers the options that you can pass when you create a +has_many+ association. For example, an association with several options might look like this:
|
||||
While Rails uses intelligent defaults that will work well in most situations, there may be times when you want to customize the behavior of the +has_many+ association reference. Such customizations can easily be accomplished by passing options when you create the association. For example, this assocation uses two such options:
|
||||
|
||||
<ruby>
|
||||
class Customer < ActiveRecord::Base
|
||||
|
@ -1585,7 +1585,7 @@ The <tt><em>collection</em>.create</tt> method returns a new object of the assoc
|
|||
|
||||
h5. Options for +has_and_belongs_to_many+
|
||||
|
||||
In many situations, you can use the default behavior for +has_and_belongs_to_many+ without any customization. But you can alter that behavior in a number of ways. This section covers the options that you can pass when you create a +has_and_belongs_to_many+ association. For example, an association with several options might look like this:
|
||||
While Rails uses intelligent defaults that will work well in most situations, there may be times when you want to customize the behavior of the +has_and_belongs_to_many+ association reference. Such customizations can easily be accomplished by passing options when you create the association. For example, this assocation uses two such options:
|
||||
|
||||
<ruby>
|
||||
class Parts < ActiveRecord::Base
|
||||
|
|
Loading…
Reference in a new issue