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

Aberta
  • Algo errado?
#1,652 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 6 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
go, react, typescript
Domínio
authentication, backend, frontend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Go
Estrelas
15.7k
Forks
1.4k
Merge médio
9d 6h
PRs com merge (30d)
8

Preparar o ambiente

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Tem um modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de apache/answer

Todas as issues de apache/answer

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.