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 摘要。