mirror of
https://github.com/discourse/discourse.git
synced 2026-08-09 21:45:25 +08:00
8faf71e3bbWhen an upcoming change was automatically enabled, the notification linked admins to the upcoming changes config page. But once a change reaches permanent status it no longer appears there (that page only lists experimental through stable) and instead surfaces on the What's New page. So if the notification was left unread until the change became permanent, clicking it dropped the admin on an empty filtered list. This resolves the change's status at click time rather than baking it into the notification. The permanent change names are now exposed to staff via the site serializer, and the notification's link checks them: if every referenced change is now permanent, it sends the admin to What's New scrolled to that change's card; otherwise it keeps the existing upcoming changes page where the still non-permanent changes remain actionable. To support the scroll, every What's New item now has a stable id anchor, and the page accepts a scrollTo query param that scrolls to and briefly highlights the matching card once the feed loads. |
||
|---|---|---|
| .. | ||
| schemas | ||
| shared | ||
| backups_spec.rb | ||
| badges_spec.rb | ||
| categories_spec.rb | ||
| groups_spec.rb | ||
| invites_spec.rb | ||
| multiple_invites_spec.rb | ||
| notifications_spec.rb | ||
| posts_spec.rb | ||
| private_messages_spec.rb | ||
| rate_limits_spec.rb | ||
| search_spec.rb | ||
| site_spec.rb | ||
| tags_spec.rb | ||
| topics_spec.rb | ||
| uploads_spec.rb | ||
| user_badges_spec.rb | ||
| users_spec.rb | ||
