5883ce95ef
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.
38 lines
1 KiB
Ruby
38 lines
1 KiB
Ruby
require 'spec_helper'
|
|
|
|
describe 'projects/edit' do
|
|
include Devise::Test::ControllerHelpers
|
|
|
|
let(:project) { create(:project) }
|
|
let(:user) { create(:admin) }
|
|
|
|
before do
|
|
assign(:project, project)
|
|
|
|
allow(controller).to receive(:current_user).and_return(user)
|
|
allow(view).to receive_messages(current_user: user,
|
|
can?: true,
|
|
current_application_settings: Gitlab::CurrentSettings.current_application_settings)
|
|
end
|
|
|
|
context 'LFS enabled setting' do
|
|
it 'displays the correct elements' do
|
|
allow(Gitlab.config.lfs).to receive(:enabled).and_return(true)
|
|
|
|
render
|
|
|
|
expect(rendered).to have_select('project_lfs_enabled')
|
|
expect(rendered).to have_content('Git Large File Storage')
|
|
end
|
|
end
|
|
|
|
context 'project export disabled' do
|
|
it 'does not display the project export option' do
|
|
stub_application_setting(project_export_enabled?: false)
|
|
|
|
render
|
|
|
|
expect(rendered).not_to have_content('Export project')
|
|
end
|
|
end
|
|
end
|