Admin: allow editing badges and creating new badges from existing rules

Aperta
  • Qualcosa non va?
#1,668 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 6 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, react, typescript
Ambito
backend, frontend, full-stack

Direzione di ricerca

Read the existing Admin → Badges implementation and the backend badge data and rule handling described in the issue; inspect the related issue #1036 for the original scope. Map how badge fields and rule parameters reach the admin interface, then identify the decisions around custom text and existing users who meet new thresholds. Done means admins can edit badges and create badges from existing rules with parameters, with those decisions resolved.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Is your enhancement request related to a problem? Please describe

Admin → Badges currently only lets an admin activate or deactivate a badge.
But each badge is already stored as data in the badge table: name,
description, icon, level, single/multiple award, and a rule (handler) with
parameters (param, e.g. {"amount":"25"}).

So a community can't, for example:

  • Lower "Good Answer" from 25 to 15 votes for a small site
  • Change a badge's icon or level
  • Add an "Epic Answer" badge at 100 votes, even though the existing
    ReachAnswerVote rule already supports it

Today these changes require editing the database directly.

Describe the solution you'd like

Extend Admin → Badges so an admin can:

  1. Edit a badge's name, description, icon, level, and rule parameters
  2. Create a new badge by choosing one of the existing rules
    (ReachAnswerVote, ReachQuestionVote, ReachAnswerAcceptedAmount, ...)
    and setting its parameters

This doesn't need any new award rules. It only exposes what the backend
already stores.

Points that may need deciding:

  • Default badge names and descriptions are i18n keys
    (badge.default_badges.*). Custom badges would need plain text, or a way
    to add translations.
  • Badge rules only run on new events, so changing a threshold won't award
    the badge to users who already qualify.

Describe alternatives you've considered

Editing the badge table directly works, but is error-prone and outside
the supported interface.

Related: #1036 (original badges feature, where admin "Badge management"
shipped as activate/deactivate only).

Lingua principale
Go
Stelle
15.7k
Fork
1.4k
Merge medio
9g 6h
PR unite (30g)
8

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/answer

Tutte le issue di apache/answer

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.