7ca55c44e0
Having exceptions is better than having silent bugs.
There are a few methods I've kept the same way they were.
The `RelatedContentScore#score_with_opposite` method is a bit peculiar:
it creates scores for both itself and the opposite related content,
which means the opposite related content will try to create the same
scores as well.
We've already got a test to check `Budget::Ballot#add_investment` when
creating a line fails ("Edge case voting a non-elegible investment").
Finally, the method `User#send_oauth_confirmation_instructions` doesn't
update the record when the email address isn't already present, leading
to the test "Try to register with the email of an already existing user,
when an unconfirmed email was provided by oauth" fo fail if we raise an
exception for an invalid user. That's because updating a user's email
doesn't update the database automatically, but instead a confirmation
email is sent.
There are also a few false positives for classes which don't have bang
methods (like the GraphQL classes) or destroying attachments.
For these reasons, I'm adding the rule with a "Refactor" severity,
meaning it's a rule we can break if necessary.
31 lines
512 B
Ruby
31 lines
512 B
Ruby
class Lock < ApplicationRecord
|
|
belongs_to :user
|
|
|
|
before_save :set_locked_until
|
|
|
|
def locked?
|
|
locked_until > Time.current
|
|
end
|
|
|
|
def set_locked_until
|
|
self.locked_until = lock_time if too_many_tries?
|
|
end
|
|
|
|
def lock_time
|
|
Time.current + (2**tries).minutes
|
|
end
|
|
|
|
def too_many_tries?
|
|
return false unless tries > 0
|
|
tries % Lock.max_tries == 0
|
|
end
|
|
|
|
def self.increase_tries(user)
|
|
find_or_create_by!(user: user).increment!(:tries).save!
|
|
end
|
|
|
|
def self.max_tries
|
|
5
|
|
end
|
|
end
|