Use page_level_alert content_for on free user cap alerts
What does this MR do and why?
This MR implements #393362 (closed) which makes the change to utilise content_for :page_level_alert
instead of content_for :free_user_cap_alert
for the free user cap alerts.
Screenshots or screen recordings
No user-facing change.
How to set up and validate locally
To validate locally, trigger a free user cap alert.
You can do this by doing the following:
- Setup GDK to simulate SaaS and restart GDK
- Sign up or sign in as a free user
- Create a private group and private project inside
- Add 4 members (Must be activated, invited doesn't count)
bin/rails c
ApplicationSetting.first.update(dashboard_limit_enabled: true, dashboard_notification_limit: 3, dashboard_limit: 5, dashboard_enforcement_limit: 5)
Feature.enable(:preview_free_user_cap)
- Go to the group info page and check alert is present
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #393362 (closed)
Edited by Ross Byrne