A platform for community discussion. Free, open, simple.
# frozen_string_literal: true
# Consolidates upcoming change notification data for both available and promoted
# changes. We do this so admins are not overwhelmed by many separate
# notifications for upcoming changes being available or promoted in cases like
# deployments where this is possible.
#
# Used in Jobs::Scheduled::NotifyAdminsOfAvailableUpcomingChanges and
# UpcomingChanges::NotifyPromotion, and only unread notifications are considered
# for merging.
class UpcomingChanges::Action::NotificationDataMerger < Service::ActionBase
MAX_STORED_NAMES = 5
option :existing_notification_data
option :new_change_name
def call
if existing_notification_data
existing_data = JSON.parse(existing_notification_data, symbolize_names: true)
names =
Array.wrap(existing_data[:upcoming_change_names] || [existing_data[:upcoming_change_name]])
humanized =
Array.wrap(
existing_data[:upcoming_change_humanized_names] ||
[existing_data[:upcoming_change_humanized_name]],
)
merged_names = (names.map(&:to_s) + [new_change_name.to_s]).uniq
merged_humanized = (humanized + [SiteSetting.humanized_name(new_change_name)]).uniq
else
merged_names = [new_change_name.to_s]
merged_humanized = [SiteSetting.humanized_name(new_change_name)]
end
{
upcoming_change_names: merged_names.first(MAX_STORED_NAMES),
upcoming_change_humanized_names: merged_humanized.first(MAX_STORED_NAMES),
count: merged_names.size,
}
end
end