1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00

Revert "Switch has_secure_token to before_save."

Mistakenly interpreted the test case as a sign that we should switch to
before_save, when the original pitch use case was intended as before_create.

Revert a3ab6ad008.
This commit is contained in:
Kasper Timm Hansen 2016-01-09 23:28:34 +01:00
parent a3ab6ad008
commit 2c1ac375c0

View file

@ -41,14 +41,13 @@ module ActiveRecord
# Note that it's still possible to generate a race condition in the database in the same way that
# {validates_uniqueness_of}[rdoc-ref:Validations::ClassMethods#validates_uniqueness_of] can.
# You're encouraged to add a unique index in the database to deal with this even more unlikely scenario.
def has_secure_token(attribute = :token, **before_save_options)
def has_secure_token(attribute = :token, **before_create_options)
# Load securerandom only when has_secure_token is used.
require 'active_support/core_ext/securerandom'
define_method("regenerate_#{attribute}") { update! attribute => self.class.generate_unique_secure_token }
before_save(before_save_options) do
send("#{attribute}=", self.class.generate_unique_secure_token) unless send("#{attribute}?")
before_create(before_create_options) do
self.send("#{attribute}=", self.class.generate_unique_secure_token) unless self.send("#{attribute}?")
end
end