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

Ouverte
  • Quelque chose ne va pas ?
#1,668 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 6 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
42/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
go, react, typescript
Domaine
backend, frontend, full-stack

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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).

Langage dominant
Go
Étoiles
15.7k
Forks
1.4k
Merge moyen
9 j 6 h
PR mergées (30 j)
8

Préparer son environnement

  • Fournit un Dockerfile ou un fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de apache/answer

Toutes les issues de apache/answer

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.