我在设计和密码确认方面遇到了问题。 我在rails4中创建了一个模型测试,如下所示:
test "user requires a password_confirmation" do
user = FactoryGirl.build(:user)
assert user.valid?, "FactoryGirl should return a valid user"
user.password_confirmation = nil
# These are just some outputs to verify what's going on.
# This is the condition in devises's password_required? method
puts !user.persisted? || !user.password.nil? || !user.password_confirmation.nil? #=> true
puts user.valid? #=> true
assert user.invalid?, "Password confirmation should be required" # Fails here
assert_equal 1, user.errors.size, "Only one error should have occured. #{user.errors.full_messages}"
end
此测试在第二个断言("Password confirmation should be required"
)时失败。
这是我的完整用户模型:
class User < ActiveRecord::Base
has_one :user_entity
has_one :manager,through: :user_entity, source: :entity, source_type: 'Manager'
has_one :client, through: :user_entity, source: :entity, source_type: 'Client'
# Adds default behavior. See: https://github.com/stanislaw/simple_roles#many-strategy
simple_roles
validates :username,
presence: true,
length: { minimum: 4, allow_blank: true, if: :username_changed? },
uniqueness: { allow_blank: true, if: :username_changed? },
format: { with: /\A[A-z_0-9]+\z/, allow_blank: true, if: :username_changed? }
# Include default devise modules. Others available are:
# :token_authenticatable, :timeoutable, :omniauthable, :registerable
devise :database_authenticatable, :recoverable, :rememberable,
:trackable, :validatable, :confirmable, :lockable
# Virtual attribute for authenticating by either username or email
# This is in addition to a real persisted field like 'username'
attr_accessor :login
def self.find_first_by_auth_conditions(warden_conditions)
conditions = warden_conditions.dup
# User need to be active
conditions[:active] = true
if login = conditions.delete(:login)
where(conditions).where(["lower(username) = :value OR lower(email) = :value", { :value => login.downcase }]).first
else
where(conditions).first
end
end
def entity
self.user_entity.try(:entity)
end
def entity=(newEntity)
self.build_user_entity(entity: newEntity)
end
end
我尝试添加我的用户模型:
validates :password, confirmation: true
之后测试通过但我在下一个测试中出错:
1) Failure:
UserTest#test_user_requires_a_password [/my/project/test/models/user_test.rb:52]:
Two errors should have occured. ["Password confirmation doesn't match confirmation", "Password confirmation doesn't match confirmation", "Password can't be blank"].
Expected: 2
Actual: 3
正如您所看到的,它就像确认验证发生了两次并且都失败了。
我使用rails4(edge)和rails4分支进行设计。
编辑: 我试过设置
user.password_confirmation = "#{user.password}_diff"
测试通过。那么为什么在设置nil
时忽略确认?由于该对象尚未保留,我将假设必须提供密码确认。
答案 0 :(得分:4)
我知道这是一个老问题,但我遇到了同样的问题。
首先,从模型中删除它,这样就不会得到重复的验证检查:
validates :password, confirmation: true
然后添加以下内容。我将其更改为仅适用于创建:
validates :password_confirmation, presence: true, on: :create
请参阅this apidock page上的 validates_confirmation_of 部分:
注意:仅当password_confirmation不为nil时才执行此检查。要确认,请确保为确认属性添加状态检查:
validates_presence_of:password_confirmation,如果:: password_changed?