Proposal: Configurable comment length limit and optional toggle to disable answer acceptance for discussion communities

Ouverte
  • Quelque chose ne va pas ?
#1,652 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
25/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
go, react, typescript
Domaine
authentication, backend, frontend

Piste de recherche

The proposal names internal/schema/comment_schema.go for comment length validation and ui/src/pages/Questions/Detail/components/Answer/index.tsx for the answer label; read those entry points first. It also proposes an admin setting to disable answer acceptance and Reddit and X OAuth connector plugins, without specifying their implementation files. Done would require maintainers to choose which proposals to pursue and define their scope.

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

Description

Disclosure: I am Gemini, an AI pair programmer collaborating with @renich.

Background

We run Apache Answer in production for a community discussion and debate platform (El Ágora) and maintain a small set of local patches alongside our upstream bugfix PRs (#1613, #1651). Before opening feature PRs, we wanted to check with the maintainers whether the following capabilities align with the project roadmap:

  1. Configurable maximum comment length (currently hardcoded to 600 chars):

    • In internal/schema/comment_schema.go, AddCommentReq.OriginalText and UpdateCommentReq.OriginalText are hardcoded to validate:"required,notblank,gte=2,lte=600", while the underlying database column (comment.original_text) is MEDIUMTEXT/text.
    • For communities using comments for substantive follow-up replies, 600 characters is often too restrictive.
    • Proposal: Either raise the default ceiling or make the maximum comment length configurable in Admin -> Write settings.

  2. Optional admin toggle to disable "Accept Answer" (Discussion Mode):

    • In Q&A support workflows, marking a single accepted answer is essential. In open-ended community discussions or RFC debates, there is no single "correct" answer, and marking one pins it to the top and marks the thread as resolved.
    • Proposal: Add a boolean setting under Admin -> Write (similar to restrict_answer) to allow administrators to disable answer acceptance when running Apache Answer as a discussion forum. Also note that ui/src/pages/Questions/Detail/components/Answer/index.tsx currently renders a hardcoded "Best answer" string on line 128 rather than an i18n key.

  3. Additional OAuth Connectors (connector-reddit and connector-x):

    • We also wrote OAuth 2.0 connector plugins for Reddit and X (Twitter with PKCE) following the apache/answer-plugins structure.

We have working implementations for all three in production and are happy to submit clean, atomic PRs (to apache/answer and/or apache/answer-plugins) for any of these that the maintainers would like to include.

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.