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

Aperta
  • Qualcosa non va?
#1,652 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
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, react, typescript
Ambito
authentication, backend, frontend

Direzione di ricerca

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.

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

Descrizione

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.

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.