Proposal: Configurable comment length limit and optional toggle to disable answer acceptance for discussion communities
维护者通常 6 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go, react, typescript
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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:
-
Configurable maximum comment length (currently hardcoded to 600 chars):
- In
internal/schema/comment_schema.go,AddCommentReq.OriginalTextandUpdateCommentReq.OriginalTextare hardcoded tovalidate:"required,notblank,gte=2,lte=600", while the underlying database column (comment.original_text) isMEDIUMTEXT/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.
- In
-
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 thatui/src/pages/Questions/Detail/components/Answer/index.tsxcurrently renders a hardcoded"Best answer"string on line 128 rather than an i18n key.
-
Additional OAuth Connectors (
connector-redditandconnector-x):- We also wrote OAuth 2.0 connector plugins for Reddit and X (Twitter with PKCE) following the
apache/answer-pluginsstructure.
- We also wrote OAuth 2.0 connector plugins for Reddit and X (Twitter with PKCE) following the
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.
- 主要语言
- Go
- 星标
- 15.7k
- 派生
- 1.4k
- 平均合并
- 9 天 6 小时
- 30 天内合并 PR
- 8
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
apache/answer 的其他 Issue
-
Hardening: cap the invite_user list size in UpdateQuestionInviteUser to bound notification fan-out可能已有人在做 @TastyHeadphones 于 47 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 6 天内回复
-
Admin AI settings silently reset the assistant prompt, which cannot be edited in the UI可能已有人在做 @Andy-Sverdlov-LucaNet 于 63 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 6 天内回复
-
难度 1/5 1-3 小时 新手友好度 75/100
维护者通常 6 天内回复
-
Server-rendered <time datetime> and JSON-LD dates ignore the site time zone (server-local wall clock labeled as UTC)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 3/5 1-2 天 新手友好度 78/100
维护者通常 6 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 42/100
维护者通常 6 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
bazel-contrib/rules_go#4784 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
POSIdev-community/aictl#40 ·
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
nebari-dev/nebari-infrastructure-core#774 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
oracle/terraform-provider-oci#2662 ·