Retrospring/app/validators/typoed_email_validator.rb

# frozen_string_literal: true

class TypoedEmailValidator < ActiveModel::EachValidator
  # this array contains "forbidden" email address endings
  INVALID_ENDINGS = [
    # without @:
    ".con",
    ".coom",
    ".cmo",
    ".mail",

    # with @:
    *%w[
      fmail.com
      gail.com
      gamil.com
      gemail.com
      gmail.cm
      gmail.co
      gmaile.com
      gmaill.com
      gmali.com
      hotamil.com
      hotmaill.com
      iclooud.com
      iclould.com
      icluod.com
    ].map { "@#{_1}" }
  ].freeze

  def validate_each(record, attribute, value)
    return if valid?(value)

    record.errors.add(attribute, :typo, message: "contains a typo")
  end

  private

  def valid?(value)
    # needs an @
    return false unless value.include?("@")

    # part after the @ needs to have at least one period
    return false if value.split("@", 2).last.count(".").zero?

    # finally, common typos
    return false if INVALID_ENDINGS.any? { value.end_with?(_1) }

    true
  end
end
add validator for typoed emails It happens quite often that people typo their email address (I blame phone keyboards for that). Catch common cases in a validator and tell the user that they have a typo in their email. Why yes, I did write the tests for this first, thanks for asking! 2022-01-11 09:37:07 -08:00			`# frozen_string_literal: true`

			`class TypoedEmailValidator < ActiveModel::EachValidator`
			`# this array contains "forbidden" email address endings`
			`INVALID_ENDINGS = [`
			`# without @:`
run Rubocop on changed files 2022-01-17 10:23:39 -08:00			`".con",`
			`".coom",`
typoed_email_validator: add new endings to the typo list 2022-06-21 10:33:51 -07:00			`".cmo",`
typoed_email_validator: add new ending to the typo list also: - consider '.mail' TLD a typo - get rid of a deprecation warning 2022-03-03 21:13:38 -08:00			`".mail",`
add validator for typoed emails It happens quite often that people typo their email address (I blame phone keyboards for that). Catch common cases in a validator and tell the user that they have a typo in their email. Why yes, I did write the tests for this first, thanks for asking! 2022-01-11 09:37:07 -08:00
			`# with @:`
			`*%w[`
			`fmail.com`
typoed_email_validator: add new endings to the typo list 2022-06-21 10:33:51 -07:00			`gail.com`
			`gamil.com`
add validator for typoed emails It happens quite often that people typo their email address (I blame phone keyboards for that). Catch common cases in a validator and tell the user that they have a typo in their email. Why yes, I did write the tests for this first, thanks for asking! 2022-01-11 09:37:07 -08:00			`gemail.com`
typoed_email_validator: add new endings to the typo list 2022-06-21 10:33:51 -07:00			`gmail.cm`
add validator for typoed emails It happens quite often that people typo their email address (I blame phone keyboards for that). Catch common cases in a validator and tell the user that they have a typo in their email. Why yes, I did write the tests for this first, thanks for asking! 2022-01-11 09:37:07 -08:00			`gmail.co`
			`gmaile.com`
			`gmaill.com`
typoed_email_validator: add new ending to the typo list 2022-01-17 10:22:34 -08:00			`gmali.com`
typoed_email_validator: add new endings to the typo list 2022-06-21 10:33:51 -07:00			`hotamil.com`
typoed_email_validator: add new ending to the typo list also: - consider '.mail' TLD a typo - get rid of a deprecation warning 2022-03-03 21:13:38 -08:00			`hotmaill.com`
typoed_email_validator: add new endings to the typo list 2022-06-21 10:33:51 -07:00			`iclooud.com`
typoed_email_validator: add new ending to the typo list 2022-04-10 00:55:05 -07:00			`iclould.com`
add validator for typoed emails It happens quite often that people typo their email address (I blame phone keyboards for that). Catch common cases in a validator and tell the user that they have a typo in their email. Why yes, I did write the tests for this first, thanks for asking! 2022-01-11 09:37:07 -08:00			`icluod.com`
			`].map { "@#{_1}" }`
			`].freeze`

			`def validate_each(record, attribute, value)`
			`return if valid?(value)`

typoed_email_validator: add new ending to the typo list also: - consider '.mail' TLD a typo - get rid of a deprecation warning 2022-03-03 21:13:38 -08:00			`record.errors.add(attribute, :typo, message: "contains a typo")`
add validator for typoed emails It happens quite often that people typo their email address (I blame phone keyboards for that). Catch common cases in a validator and tell the user that they have a typo in their email. Why yes, I did write the tests for this first, thanks for asking! 2022-01-11 09:37:07 -08:00			`end`

			`private`

			`def valid?(value)`
			`# needs an @`
run Rubocop on changed files 2022-01-17 10:23:39 -08:00			`return false unless value.include?("@")`
add validator for typoed emails It happens quite often that people typo their email address (I blame phone keyboards for that). Catch common cases in a validator and tell the user that they have a typo in their email. Why yes, I did write the tests for this first, thanks for asking! 2022-01-11 09:37:07 -08:00
			`# part after the @ needs to have at least one period`
run Rubocop on changed files 2022-01-17 10:23:39 -08:00			`return false if value.split("@", 2).last.count(".").zero?`
add validator for typoed emails It happens quite often that people typo their email address (I blame phone keyboards for that). Catch common cases in a validator and tell the user that they have a typo in their email. Why yes, I did write the tests for this first, thanks for asking! 2022-01-11 09:37:07 -08:00
			`# finally, common typos`
			`return false if INVALID_ENDINGS.any? { value.end_with?(_1) }`

			`true`
			`end`
			`end`