[VS Code Extension] listing emitter libraries to install is confusing in TypeSpec project scaffolding scenario

[josefree]

TypeSpec: 0.67.1
Repo steps

1. install TypeSpec extension in VS Code
2. click "Create TypeSpec Project" and select the template "Generic REST API"
   I found it will list all available emitters for optional install.
   

Listing all available code emitters here is confusing. "Generic REST API" shows the purpose of setting up an API definition. Emitter libraries can be prompted to install when users choose "Emit from TypeSpec".

[RodgeFu]

The list is not controlled by vscode extension but the template defined in compiler. You can also check the tsp init for the same list. @timotheeguerin , @allenjzhang, to comment on the lists defined in the template. thx.

[timotheeguerin]

yeah those just present whatever the template is showing and is shared with tsp init, why do you think it is confusing? This was all requested, designed to be like that.

Hiding emitters behind the emit from typespec functionality is not a great experience:

1. Most people will most likely never even see this functionality
2. and to be honest even less likely to use it again with how many steps you have to do everytime when you can just run tsp compile
3. The goal is to setup your project, you most likely want to do something else than just write the TypeSpec and having them in a fully available state is a better option

[microsoft-github-policy-service]

Hi @@josefree. Since there hasn't been recent engagement, we're going to close this out. Please feel free to reopen if you have any further questions or concerns.