gitlab-org--gitlab-foss/app/mailers
Sean McGivern 5883ce95ef current_application_settings belongs on Gitlab::CurrentSettings
The initializers including this were doing so at the top level, so every object
loaded after them had a `current_application_settings` method. However, if
someone had rack-attack enabled (which was loaded before these initializers), it
would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
have that method.

To fix this:

1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
   `Object.new.current_application_settings` to work.
2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
   like that in several places.
3. Change the initializers to use that new form.
2017-08-31 13:38:33 +01:00
..
emails Speed up Group#user_ids_for_project_authorizations 2017-08-14 12:47:15 +01:00
abuse_report_mailer.rb Make AbuseReportMailer responsible for knowing if it should deliver 2016-01-04 18:59:25 -05:00
base_mailer.rb current_application_settings belongs on Gitlab::CurrentSettings 2017-08-31 13:38:33 +01:00
devise_mailer.rb use common devise layout and use heading style 2017-06-13 22:36:45 +02:00
email_rejection_mailer.rb Generate valid Message-ID in email rejection mailer 2016-01-30 18:30:53 +08:00
notify.rb Rename many path_with_namespace -> full_path 2017-08-01 07:26:58 +02:00
repository_check_mailer.rb Fix code for cops 2017-02-23 09:31:57 -06:00