discourse/lib/validators/email_setting_validator.rb

# frozen_string_literal: true

class EmailSettingValidator
  def initialize(opts = {})
    @opts = opts
  end

  def valid_value?(val)
    return true if val.blank?
    EmailAddressValidator.valid_value?(val)
  end

  def error_message
    I18n.t("site_settings.errors.invalid_email")
  end
end
DEV: enable frozen string literal on all files This reduces chances of errors where consumers of strings mutate inputs and reduces memory usage of the app. Test suite passes now, but there may be some stuff left, so we will run a few sites on a branch prior to merging 2019-05-02 17:17:27 -05:00			`# frozen_string_literal: true`

Add ability to run validation on site settings. notification_email and other email address settings are now validated. 2014-06-09 14:17:36 -05:00			`class EmailSettingValidator`
Add a way to validate min and max value of an integer site setting 2014-06-12 17:03:03 -05:00			`def initialize(opts = {})`
			`@opts = opts`
			`end`

			`def valid_value?(val)`
DEV: pull email address validation out to a new EmailAddressValidator We validate the format of email addresses in many places with a match against a regex, often with very slightly different syntax. Adding a separate EmailAddressValidator simplifies the code in a few spots and feels cleaner. Deprecated the old location in case someone is using it in a plugin. No functionality change is in this commit. Note: the regex used at the moment does not support using address literals, e.g.: * localpart@[192.168.0.1] * localpart@[2001:db8::1] 2022-02-17 19:12:51 -06:00			`return true if val.blank?`
			`EmailAddressValidator.valid_value?(val)`
Add ability to run validation on site settings. notification_email and other email address settings are now validated. 2014-06-09 14:17:36 -05:00			`end`

Add validation of string site settings with regex, and min and max lengths 2014-06-18 09:49:21 -05:00			`def error_message`
Add ability to run validation on site settings. notification_email and other email address settings are now validated. 2014-06-09 14:17:36 -05:00			`I18n.t("site_settings.errors.invalid_email")`
			`end`
			`end`