mirror of
https://gh.wpcy.net/https://github.com/discourse/discourse.git
synced 2026-05-09 06:15:57 +08:00
5cef23ef63
Adds four tiered badges to discourse-topic-voting so topic authors are recognized when their ideas get traction: - Daydreamer (Bronze, 1 vote) - Brainstormer (Silver, 5 votes) - Innovator (Silver, 15 votes) - Visionary (Gold, 25 votes) Badges are multi-grant and tied to the qualifying topic's first post, so a user earns each tier once per topic that reaches the threshold. Self-votes (voting on your own topic) are excluded. All badges are disabled by default; the Silver and Gold tiers (Brainstormer, Innovator, Visionary) allow the badge to be used as a title when enabled. <img width="287" height="216" alt="image" src="https://github.com/user-attachments/assets/3a84c2b2-6157-4504-b5a5-45e7c660e90c" /> ### How it is wired - `Votes::Cast` enqueues a `BackfillBadges` job after a vote is cast. - `TopicMerger.merge` and `VoteReclaim` also enqueue the job so merged or reclaimed topics are re-evaluated immediately rather than having to wait for the daily consistency pass. - The job calls `BadgeGranter.backfill` scoped to the topic's first post. Queries join `badge_posts`, which already filters out deleted and unlisted topics, read-restricted categories, and categories with `allow_badges` disabled. - Each query returns `granted_at` as the timestamp of the Nth qualifying vote (via `ROW_NUMBER()`), so every tier reflects when that threshold was actually crossed rather than when the most recent vote landed. - Revocation (vote removed, topic deleted, category changed) runs on the daily full backfill via `auto_revoke`, consistent with how discourse-solved handles the same pattern. ### Notification handling To avoid "granted badge" notification avalanches when the feature is first enabled on a community with years of existing votes, core now exposes a `:badge_granter_suppress_notification` modifier. The plugin registers it and suppresses notifications for its four badges when the qualifying vote is older than 2 weeks. Combined with the per-tier `granted_at`, this means only the tier the author just crossed produces a notification; lower tiers whose threshold was reached long ago stay silent. Ref - t/182304
25 lines
824 B
Ruby
25 lines
824 B
Ruby
# frozen_string_literal: true
|
|
|
|
[
|
|
["Daydreamer", BadgeType::Bronze, 1, false],
|
|
["Brainstormer", BadgeType::Silver, 5, true],
|
|
["Innovator", BadgeType::Silver, 15, true],
|
|
["Visionary", BadgeType::Gold, 25, true],
|
|
].each do |name, level, count, allow_title|
|
|
Badge.seed(:name) do |badge|
|
|
badge.name = name
|
|
badge.default_icon = "vote-up-filled"
|
|
badge.badge_type_id = level
|
|
badge.default_badge_grouping_id = BadgeGrouping::Community
|
|
badge.query = DiscourseTopicVoting::BadgeQueries.for_threshold(count)
|
|
badge.listable = true
|
|
badge.target_posts = true
|
|
badge.multiple_grant = true
|
|
badge.default_enabled = false
|
|
badge.default_allow_title = allow_title
|
|
badge.trigger = Badge::Trigger::None
|
|
badge.auto_revoke = true
|
|
badge.show_posts = true
|
|
badge.system = true
|
|
end
|
|
end
|
