[UWP] Initialize empty input object for OpenUrl action invoke #5336
Conversation
This file contains 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
paulcam206
approved these changes
Jan 28, 2021
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.
Related Issue
Fixes #5330
Description
As part of the work to implement
"associatedInputs":"none", the action invoke code was refactored in such a way that OpenUrl action invokes no longer had an Inputs object. Although this object was always empty for OpenUrl types, our Visualizer depended on it being non-null. Because it's technically a breaking change (that actually broke the visualizer), I restored the old behavior where OpenUrl action invocations have an empty but non-null inputs object.Sample Card
ActivityUpdate.json scenario card
How Verified
Confirmed OpenUrl button now works as expected
Microsoft Reviewers: Open in CodeFlow