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

Offen
  • Stimmt etwas nicht?
#1,652 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 6 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
go, react, typescript
Bereich
authentication, backend, frontend

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Go
Sterne
15.7k
Forks
1.4k
Ø Merge
9 T. 6 Std.
Gemergte PRs (30 T.)
8

Entwicklungsumgebung

  • Enthält ein Dockerfile oder eine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus apache/answer

Alle Issues in apache/answer

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.