Repository navigation
Bind form submit continuations to the command response - #273
Merged
Merged
Conversation
Contributor
Author
|
Reviewer notes (not release notes)
|
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.
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
onSubmitinteraction 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 withoutonSubmitbehave as before. See Command responses and form continuations. (Forms on submit and binding command responses in continuations #53)commandResponsebinding source reads the successful command response inside a continuation: the whole response with an empty path, or a member such asprojectIdoraddress.street.false,0and 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) andResponseBindings.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)