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

Abierto
  • ¿Algo no está bien?
#1,652 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 6 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go, react, typescript
Área
authentication, backend, frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
15.7k
Forks
1.4k
Merge medio
9 d 6 h
PR fusionados (30 d)
8

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/answer

Todos los issues de apache/answer

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.