Missing step to confirm TypeSpec Emitter

[xiaohua899]

Description

After selecting the language when Generate from TypeSpec, there is no step to confirm the TypeSpec emitter. Go directly to the generate step.

Repro steps

1. Install the typespec extension.
2. Install @typespec/compiler: npm install -g @typespec/compiler.
3. Typing >TypeSpec: Generate from TypeSpec and Click the command.
4. Choose a project.
5. Select Emitter Type. (Client Code or Protocol Schema)
6. Select a language.(e.g. DotNet)

Environment

• TypeSpec for VS Code extension version: 0.63.0
• TypeSpec compiler/CLI version: 0.63.0
• OS: Windows, Linux
• Emitter Type: Client Code, Protocol Schema
• Language: Python, Java, JavaScript, .NET

Expected behavior

There should be a prompt Here are libraries to install or update, and TypeSpec emitters to install and their minimum requirements.

@RodgeFu, @chunyu3 and @msyyc for notification.

[chunyu3]

Hello @xiaohua899 This is already implemented. I am afraid your vscode extension is out-of-date.
Please download the latest version in #5312 (comment) to test.

Thanks.

[xiaohua899]

@chunyu3 This has been implemented in #5312 (comment).
But there is one question I need to confirm with you.
When generating code for a language in folderA, this prompt will appear. However, when opening another main.tsp in FolderA and generating the same language, this prompt will not appear. Then, when opening folderB to generate the same language, this prompt will still appear.
Is this expected?

[chunyu3]

@chunyu3 This has been implemented in #5312 (comment). But there is one question I need to confirm with you. When generating code for a language in folderA, this prompt will appear. However, when opening another main.tsp in FolderA and generating the same language, this prompt will not appear. Then, when opening folderB to generate the same language, this prompt will still appear. Is this expected?

The emitter library is installed in the typespec project folder, not global. so FolderA and FolderB belong to different typespec project. So when emitter library is installed for FolderA, but not for FolderB, this page is show when generate the the language for FolderB

[xiaohua899]

@chunyu3 After our recent testing, we found that the UI during testing is a little different from the previous version.
When Generate from TypeSpec, the steps are: Select an emitter type -> Select a language -> Select an emitter for code generation -> Here are the libraries to install or update. The Select an emitter for code generation step did not exist in previous version. Is this the expected result?

[chunyu3]

@chunyu3 After our recent testing, we found that the UI during testing is a little different from the previous version. When Generate from TypeSpec, the steps are: Select an emitter type -> Select a language -> Select an emitter for code generation -> Here are the libraries to install or update. The Select an emitter for code generation step did not exist in previous version. Is this the expected result?

@xiaohua899 We add a new feature. When there are emitters configured in tspConfig.yaml, this page will show as first page to support quick path scenario to regen existing code.

[xiaohua899]

It has been fixed and we will close this issue.