Add Quickstart reference sample functionality, plus UX fixes (accessibility, data binding) #2857
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.
Summary of the pull request
This change adds functionality to the new Quickstart Playground feature to allow implementing extensions to show the user any reference data that went into producing the project.
References and relevant issues
Detailed description of the pull request / Additional comments
In the Quickstart Playground experimental feature, this change exposes a button that the user can click on in the user interface to view the sample directory corresponding to the closest "match" for the user's input prompt (there are supporting changes being made on the Azure extension side that pair with this change). It also includes the supporting scaffolding in the ViewModel to enable this.
As part of this change, we also fix an issue with the View retaining stale data (i.e., progress bar state and last-opened file) from the prior project generation attempt.
This change also addresses some accessibility issues:
Validation steps performed
I manually ran through the new behavior and verified that I could view the reference sample (the explorer window below was opened via the link under the Generate button).
I ran Narrator and Accessibility Insights cleanly, and visually verified the behavior of the controls that are now wrapping.
PR checklist