feat(app-shell): FlowRunner — render & resume interactive screen-flows#1428
Merged
Conversation
A `type:'flow'` action whose run pauses at a `screen` node now opens a FlowRunner modal that renders the screen fields, POSTs the values to the framework resume endpoint, and advances to the next screen or closes + refreshes on completion. ObjectView + RecordDetailView detect the paused-screen launch response and open the runner; list_item actions pass the row id (`_rowRecord.id`) as the flow's recordId. Verified in-browser: showcase task row → Reassign… → form → submit → reassigned.
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Completes the UI half of the screen-flow runtime. A
type: 'flow'action whose run pauses at ascreennode now opens aFlowRunnermodal that renders the screen's fields, POSTs the values to the framework resume endpoint (POST /api/v1/automation/{flow}/runs/{runId}/resume), and advances to the next screen or closes + refreshes on completion. Previously such flows launched server-side but the screen was never rendered — the input was never collected (the showcase Reassign Wizard'sapplystep failed).FlowRunnercomponent — rendersscreen.fields(text / textarea / number / boolean / select), runs the submit→resume loop, surfaces flow errors.ObjectView+RecordDetailViewflow handlers detect the paused-screen launch response ({ status:'paused', runId, screen }) and open the runner. Forlist_itemactions the row's id (_rowRecord.id) now flows in as the flow'srecordId.Verification (in-browser)
Showcase task grid → row "更多操作" → "Reassign…" → FlowRunner renders the "New Assignee" field → submit
casey@example.com→ run resumes →update_record→ task "Audit current IA" reassigned ada→casey, dialog closes. app-shell typecheck clean.Pairs with the framework screen-flow runtime (objectstack-ai/framework#1452:
@objectstack/service-automation+@objectstack/runtime).