d0d681a44b
We were inconsistent on this one. I consider it particularly useful when a method starts with a `return` statement. In other cases, we probably shouldn't have a guard rule in the middle of a method in any case, but that's a different refactoring.
34 lines
580 B
Ruby
34 lines
580 B
Ruby
class EvaluationCommentEmail
|
|
attr_reader :comment
|
|
|
|
def initialize(comment)
|
|
@comment = comment
|
|
end
|
|
|
|
def commentable
|
|
comment.commentable
|
|
end
|
|
|
|
def to
|
|
@to ||= related_users
|
|
end
|
|
|
|
def subject
|
|
I18n.t("mailers.evaluation_comment.subject")
|
|
end
|
|
|
|
def can_be_sent?
|
|
commentable.present? && to.any?
|
|
end
|
|
|
|
private
|
|
|
|
def related_users
|
|
return [] if comment.commentable.nil?
|
|
|
|
comment.commentable
|
|
.admin_and_valuator_users_associated
|
|
.reject { |associated_user| associated_user.user == comment.author }
|
|
end
|
|
end
|