adrastogi
commented
4 months ago We are following up separately on build warnings from the pipeline (cc: @manodasanW).
Closed adrastogi closed 4 months ago
adrastogi
commented
4 months ago We are following up separately on build warnings from the pipeline (cc: @manodasanW).
Summary of the pull request
This change adds the sample projects that the Azure extension's Quickstart provider implementation uses as input when generating a new project. The extension passes back a URI to the one that most closely matches the user's supplied prompt.
References and relevant issues
Detailed description of the pull request / Additional comments
Our extension that can be used with the experimental Dev Home Quickstart Playground feature includes with it a range of basic devcontainer sample projects that cover different technology types and scenarios. If the user chooses this extension for generating a new project, as part of that process, the extension will try to match up the user's prompt against one of these projects so that they can be used as examples to help guide the language model in producing a project that matches the user's goals. The extension uses the Quickstart API surface to point to the directory of the sample that was used in the generation attempt. The samples are included as assets in the package. As part of this, I had to make one small change to the .editorconfig settings to exclude the 'Hello, world' C# file from being analyzed.
Validation steps performed
I manually tested the scenario in conjunction with the incoming support in Dev Home. In the screenshot below, the path opened by explorer comes from the extension.
PR checklist