Module: ActiveModel::Validations::HelperMethods

Defined in:
lib/common_lib/active_model/validations/absence.rb,
lib/common_lib/active_model/validations/past_date.rb,
lib/common_lib/active_model/validations/complete_date.rb

Instance Method Summary collapse

Instance Method Details

#validates_absence_of(*attr_names) ⇒ Object

Validates that the specified attributes are blank (as defined by Object#blank?). Happens by default on save. Example:

class Person < ActiveRecord::Base validates_absence_of :first_name end

The first_name attribute must be in the object and it cannot be blank.

If you want to validate the absence of a boolean field (where the real values are true and false), you will want to use validates_inclusion_of :field_name, :in => [true, false].

This is due to the way Object#blank? handles boolean values: false.blank? # => true.

Configuration options:

  • :message - A custom error message (default is: "can't be blank").
  • :on - Specifies when this validation is active. Runs in all validation contexts by default (+nil+), other options are :create and :update.
  • :if - Specifies a method, proc or string to call to determine if the validation should

occur (e.g. :if => :allow_validation, or :if => Proc.new { |user| user.signup_step > 2 }). The method, proc or string should return or evaluate to a true or false value.

  • :unless - Specifies a method, proc or string to call to determine if the validation should

not occur (e.g. :unless => :skip_validation, or :unless => Proc.new { |user| user.signup_step <= 2 }). The method, proc or string should return or evaluate to a true or false value.

  • :strict - Specifies whether validation should be strict. See ActiveModel::Validation#validates! for more information


73
74
75
 
# File 'lib/common_lib/active_model/validations/absence.rb', line 73

def validates_absence_of(*attr_names)
  validates_with AbsenceValidator, _merge_attributes(attr_names)
end

#validates_complete_date_for(*attr_names) ⇒ Object

Validates that the specified attributes contain a complete date. Happens by default on save. Example:

class Person < ActiveRecord::Base validates_complete_date_for :dob end

The first_name attribute must be in the object and it cannot be blank.

If you want to validate the absence of a boolean field (where the real values are true and false), you will want to use validates_inclusion_of :field_name, :in => [true, false].

This is due to the way Object#blank? handles boolean values: false.blank? # => true.

Configuration options:

  • :message - A custom error message (default is: "can't be blank").
  • :on - Specifies when this validation is active. Runs in all validation contexts by default (+nil+), other options are :create and :update.
  • :if - Specifies a method, proc or string to call to determine if the validation should

occur (e.g. :if => :allow_validation, or :if => Proc.new { |user| user.signup_step > 2 }). The method, proc or string should return or evaluate to a true or false value.

  • :unless - Specifies a method, proc or string to call to determine if the validation should

not occur (e.g. :unless => :skip_validation, or :unless => Proc.new { |user| user.signup_step <= 2 }). The method, proc or string should return or evaluate to a true or false value.

  • :strict - Specifies whether validation should be strict. See ActiveModel::Validation#validates! for more information


133
134
135
 
# File 'lib/common_lib/active_model/validations/complete_date.rb', line 133

def validates_complete_date_for(*attr_names)
  validates_with CompleteDateValidator, _merge_attributes(attr_names)
end

#validates_past_date_for(*attr_names) ⇒ Object

Validates that the specified attributes contain a date in the past. Happens by default on save. Example:

class Person < ActiveRecord::Base validates_past_date_for :dob end

The first_name attribute must be in the object and it cannot be blank.

If you want to validate the absence of a boolean field (where the real values are true and false), you will want to use validates_inclusion_of :field_name, :in => [true, false].

This is due to the way Object#blank? handles boolean values: false.blank? # => true.

Configuration options:

  • :message - A custom error message (default is: "can't be blank").
  • :on - Specifies when this validation is active. Runs in all validation contexts by default (+nil+), other options are :create and :update.
  • :if - Specifies a method, proc or string to call to determine if the validation should

occur (e.g. :if => :allow_validation, or :if => Proc.new { |user| user.signup_step > 2 }). The method, proc or string should return or evaluate to a true or false value.

  • :unless - Specifies a method, proc or string to call to determine if the validation should

not occur (e.g. :unless => :skip_validation, or :unless => Proc.new { |user| user.signup_step <= 2 }). The method, proc or string should return or evaluate to a true or false value.

  • :strict - Specifies whether validation should be strict. See ActiveModel::Validation#validates! for more information


116
117
118
 
# File 'lib/common_lib/active_model/validations/past_date.rb', line 116

def validates_past_date_for(*attr_names)
  validates_with PastDateValidator, _merge_attributes(attr_names)
end