Evolve logic & UX | Rethink forms | become a must have asset to nextcloud core

未关闭
#2,871 8 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
javascript

调研方向

该 issue 未指定文件、测试或入口点。首先将提案拆分为所述的 P0 领域——FDS v1 和验证、条件逻辑、Creator、webhooks 以及 Flow 集成——并使用验收标准定义每个部分的完成情况。

由索引模型根据 Issue 内容生成。

描述

discussion overview

Evolve Nextcloud Forms to SurveyJS class with a schema and logic core and a creator UX

Summary
Forms is intentionally simple and works for quick polls. Many Nextcloud deployments (public sector, education, multi-section clubs, enterprises) need conditional logic, governance, and integrations. Without these, users build workarounds or move to external SaaS. A schema-first model with a small expression engine and a creator UI covers these needs while keeping existing simple use cases intact.

Target parity (functional, not 1:1)

  • Runtime: JSON schema with conditional visibility (visibleIf), computed values, answer piping, multi-page flow, dynamic or repeating groups, richer question types, i18n, accessible rendering.
  • Creator: drag-and-drop builder, property grid, live preview, theme editor. JSON round-trip identical to the runtime schema.
  • Events and integration: stable REST plus signed webhooks on submission. First-class bridges to Flow, Tables, Deck, and external systems.

Why this helps maintainers

  • Fewer one-off requests. An expression and visibility layer reduces long-tail “add setting X” tickets.
  • Clearer boundaries. Definition, renderer, and submission or storage are separated, which improves tests and avoids UI or business-logic leaks.
  • Easier contributions. A documented schema with a validator makes reviews contract based.
  • Lower support load. A consistent model with draft or publish, versioning, and audit removes many state mismatch bugs.

Minimal architectural changes (incremental, backward compatible)

  1. Add FDS v1 (Form Definition Schema) and a validator on server and build time.
  2. Add a small expression engine (JSON-Logic-like) for visibility, validation, and computed defaults.
  3. Implement a Creator that edits FDS v1 (drag-and-drop, property grid, live preview).
  4. Emit submission events as signed webhooks and document Flow recipes.
  5. Provide a v0 to v1 converter for existing simple forms. Keep legacy rendering read compatible during transition.

Acceptance criteria for P0

  • A form that uses conditional visibility, computed fields, and a repeating group renders correctly and validates on the server.
  • The Creator can build the same form with JSON round-trip parity.
  • Submissions trigger webhooks and work with Flow. The API remains stable.
  • WCAG-compliant rendering and an audit log for schema publishes and changes.

Ecosystem impact

If Forms reaches SurveyJS class, many organizations can stay on Nextcloud instead of paying for Typeform, SurveyMonkey, or Qualtrics. Data remains on premises and within GDPR. Total cost of ownership drops for public sector, education, NGOs, and clubs. Cross-app value increases: submissions can start Flow automations, create Deck cards, populate Tables or Collectives, notify in Talk, or land in Files with auditability. Hosting partners get a clear upsell for self-hosted enterprise forms. A stable schema and API invite third-party validators, widgets, and connectors. This moves Nextcloud from a files-plus-collaboration hub toward a process platform used daily for business-critical work.

主要语言
JavaScript
星标
385
派生
133
平均合并
7 小时 54 分钟
30 天内合并 PR
157

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nextcloud/forms 的其他 Issue

查看 nextcloud/forms 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。