Release v4.84.0

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. (#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. (#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. (#53)