mengw15 commented on issue #8011: URL: https://github.com/apache/texera/issues/8011#issuecomment-5478342862
A product-design question on the gating model, raised while reviewing formview-pr2 (the answer bears directly on that PR's column and endpoints, and on pr8a/pr11 later, so worth settling before more slices land): Right now Form View is a per-workflow capability the author must switch on, and the form page redirects away when the workflow isn't marked. An alternative model: the form is always available for every workflow — with zero exposed inputs it degrades to a one-click run page (Run + results), and exposed bindings only enrich it. That removes the empty-page problem the flag guards against (the page always has at least Run + results), dissolves the enable-before-authoring bootstrap, and gives read-only visitors a coherent run-only surface instead of needing a redirect. The per-workflow bit could then shrink from a capability gate to a default-entry preference (open in form vs canvas by default) — or disappear entirely: the landing view can be derived from whether the content carries any bindings, if the dashboard doesn't need to mark form workflows without reading their content. A concrete simplification: the gate currently has to be inherited along every copy path (duplicate, hub clone, and version clone — where the flag isn't versioned, so a version clone gets today's setting regardless of the content it restores); in the always-available model those questions don't exist. The open questions this model has to answer: what an un-curated form shows in its results area (default to the operators already marked for result viewing?), and whether a run-without-context page should be reachable on every workflow at all (the current flag also doubles as the author's "this is sensible to run as a black box" signal). Curious whether you considered this shape. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
