Skip to content

Bind form submit continuations to the command response - #273

Merged
woksin merged 11 commits into
mainfrom
scene-53-command-response
Oct 26, 2026
Merged

woksin merged 11 commits into
mainfrom
scene-53-command-response

Conversation

@woksin

@woksin woksin commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

A form can now continue after its command succeeds, using values from the command's response, for example to navigate to the item it just created.

Added

  • Forms accept onSubmit interaction actions. These run once, after the native command succeeds, and never on validation, authorization or exception failures. The command is not executed a second time. Forms without onSubmit behave as before. See Command responses and form continuations. (Forms on submit and binding command responses in continuations #53)
  • The commandResponse binding source reads the successful command response inside a continuation: the whole response with an empty path, or a member such as projectId or address.street. false, 0 and an empty string are valid values. A nested command's response shadows the outer one, a failed command's response is never visible, and sibling actions do not see each other's responses. (Forms on submit and binding command responses in continuations #53)
  • validateResponseBindings (TypeScript) and ResponseBindings.Validate (C#) check every response binding against producer-supplied response and destination contracts before anything runs. A reference to an unknown or void response, a missing or inherited member, an unsupported path, an incompatible destination, or a null where the contract does not allow one is rejected. At runtime, an unavailable or incompatible response value reports a finding and stops the continuation instead of acting on an undefined value. (Forms on submit and binding command responses in continuations #53)

@woksin woksin added the minor label Oct 26, 2026
@woksin woksin self-assigned this Oct 26, 2026
@woksin

woksin commented Oct 26, 2026

Copy link
Copy Markdown
Contributor Author

Reviewer notes (not release notes)

  • Local gates at dc166bf: Release build (warnings as errors), Release specs (Engine 180, Model 43), full yarn ci, verify-packages, verify-blueprints, Storybook, browser shards — all green.
  • Review: whole-change full review round 1 (2 blocking findings fixed), round 2 full delta passed at c3b4ba8, round 3 quick delta passed at dc166bf.
  • Two minor advisories left in formSuccessContinuation.ts (non-blocking).
  • PR authored as woksin, so assigned only (no self review request).

@woksin
woksin merged commit fa5936d into main Oct 26, 2026
10 of 11 checks passed
@woksin
woksin deleted the scene-53-command-response branch October 26, 2026 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant