gitlab-org--gitlab-foss/spec/views
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
..
admin/dashboard current_application_settings belongs on Gitlab::CurrentSettings 2017-08-31 13:38:33 +01:00
ci Change all :empty_project to :project 2017-08-02 17:47:31 -04:00
devise/shared current_application_settings belongs on Gitlab::CurrentSettings 2017-08-31 13:38:33 +01:00
help current_application_settings belongs on Gitlab::CurrentSettings 2017-08-31 13:38:33 +01:00
layouts current_application_settings belongs on Gitlab::CurrentSettings 2017-08-31 13:38:33 +01:00
notify Ensure all project factories use :repository trait or :empty_project 2017-08-01 14:51:52 -04:00
profiles Update test to use single quotes and Four-Phase test conventions 2017-06-15 11:38:12 +00:00
projects current_application_settings belongs on Gitlab::CurrentSettings 2017-08-31 13:38:33 +01:00
shared current_application_settings belongs on Gitlab::CurrentSettings 2017-08-31 13:38:33 +01:00