Skip to content

Commit

Permalink
Remove comments since now matchers can be used in the negative form.
Browse files Browse the repository at this point in the history
  • Loading branch information
josevalim committed Jul 16, 2009
1 parent a1a529c commit 2354836
Show file tree
Hide file tree
Showing 2 changed files with 0 additions and 25 deletions.
Expand Up @@ -53,19 +53,6 @@ def protected_attributes

# Ensures that the attribute can be set on mass update.
#
# Beware that when used in the negative form, this matcher fails if any of
# the values fail. For example, let's assume we have a accessible and a
# protected attribute called :accessible and :protected. The following
# assertion WILL pass:
#
# should_not_allow_mass_assignment_of :protected, :accessible
#
# If you want to assert that all values fail, you have to do:
#
# %w(first_protected second_protected).each do |protected|
# should_not_allow_mass_assignment_of protected
# end
#
# == Examples
#
# should_allow_mass_assignment_of :email, :name
Expand Down
Expand Up @@ -64,18 +64,6 @@ def interpolation_options

# Ensures that the attribute can be set to the given values.
#
# Beware that when used in the negative form, this matcher fails if any of
# the values fail. For example, let's assume we have a valid and invalid
# value called "valid" and "invalid". The following assertion WILL pass:
#
# should_not_allow_values_for :attribute, "valid", "invalid"
#
# If you want to assert that all values fail, you have to do:
#
# %w(first_invalid second_invalid).each do |invalid|
# should_not_allow_values_for invalid
# end
#
# == Options
#
# * <tt>:allow_nil</tt> - when supplied, validates if it allows nil or not.
Expand Down

0 comments on commit 2354836

Please sign in to comment.