3
\$\begingroup\$

I have two classes responsible for attributes validation:

class NameValidator < ActiveModel::EachValidator
 def validate_each(record, attribute, value)
 message = options.fetch(:message, I18n.t('errors.attributes.name.invalid'))
 record.errors[attribute] << message unless NameValidator.valid_name?(value)
 end
 def self.valid_name?(name)
 name =~ /\A[a-z][\w\p{Blank}]+\z/i
 end
end

and the second one:

class EmailValidator < ActiveModel::EachValidator
 def validate_each(record, attribute, value)
 message = options.fetch(:message, I18n.t('errors.attributes.email.invalid'))
 record.errors[attribute] << message unless EmailValidator.valid_email?(value)
 end
 def self.valid_email?(email)
 email =~ /\A.+@.+\..+\z/i
 end
end

They're basically the same. Should I inherit them from one class with protected utility methods or what?

Jamal
35.2k13 gold badges134 silver badges238 bronze badges
asked Jan 25, 2016 at 23:07
\$\endgroup\$
1
  • \$\begingroup\$ Can you show how you're using these validators? Couldn't you use validates_format_of instead? \$\endgroup\$ Commented Jan 26, 2016 at 1:06

1 Answer 1

5
\$\begingroup\$

By creating a base class and then inheriting from it, you end up with no duplication and with an architecture that can be easily extended.

I don't think that you should bother having valid? as protected. Calling valid? from outside is a common use case and doesn't violate encapsulation.

class Validator < ActiveModel::EachValidator
 def validate_each(record, attribute, value)
 message = options.fetch(:message, I18n.t('errors.attributes.name.invalid'))
 record.errors[attribute] << message unless self.valid?(value)
 end
 def self.valid?(value)
 raise NotImplementedError
 end
end
class NameValidator < Validator
 def self.valid?(value)
 value =~ /\A[a-z][\w\p{Blank}]+\z/i
 end
end
class EmailValidator < Validator
 def self.valid?(value)
 value =~ /\A.+@.+\..+\z/i
 end
end
answered Jan 25, 2016 at 23:19
\$\endgroup\$
2
  • 1
    \$\begingroup\$ Welcome to Code Review! Good job on your first answer \$\endgroup\$ Commented Jan 25, 2016 at 23:35
  • \$\begingroup\$ The other reason to keep valid? public is that you can unit test it. \$\endgroup\$ Commented Jan 28, 2016 at 5:04

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.