7684217d68
This enforces the terms in the web application. These cases are
specced:
- Logging in: When terms are enforced, and a user logs in that has not
accepted the terms, they are presented with the screen. They get
directed to their customized root path afterwards.
- Signing up: After signing up, the first screen the user is presented
with the screen to accept the terms. After they accept they are
directed to the dashboard.
- While a session is active:
- For a GET: The user will be directed to the terms page first,
after they accept the terms, they will be directed to the page
they were going to
- For any other request: They are directed to the terms, after they
accept the terms, they are directed back to the page they came
from to retry the request. Any information entered would be
persisted in localstorage and available on the page.
19 lines
658 B
Ruby
19 lines
658 B
Ruby
module TermsHelper
|
|
def enforce_terms
|
|
stub_env('IN_MEMORY_APPLICATION_SETTINGS', 'false')
|
|
settings = Gitlab::CurrentSettings.current_application_settings
|
|
ApplicationSettings::UpdateService.new(
|
|
settings, nil, terms: 'These are the terms', enforce_terms: true
|
|
).execute
|
|
end
|
|
|
|
def accept_terms(user)
|
|
terms = Gitlab::CurrentSettings.current_application_settings.latest_terms
|
|
Users::RespondToTermsService.new(user, terms).execute(accepted: true)
|
|
end
|
|
|
|
def expect_to_be_on_terms_page
|
|
expect(current_path).to eq terms_path
|
|
expect(page).to have_content('Please accept the Terms of Service before continuing.')
|
|
end
|
|
end
|