Extension: Generate from TypeSpec does not work with client.tsp as entrypoint file

[swathipil]

Describe the bug

I've copied over the main.tsp and client.tsp from [this] folder into a test project following these instructions.

I tried to "Generate from TypeSpec" with the client.tsp and Python emitter specified, but it's still using main.tsp as the entrypoint file and the client.tsp changes are not being applied during Python client generation.

tspconfig.yaml:

parameters:
  "service-dir":
    default: "sdk/schemaregistry"
  "dependencies":
    "additionalDirectories": []
    default: ""
emit:
  - "@azure-tools/typespec-autorest"
  - "@typespec/http-client-python"
linter:
  extends:
    - "@azure-tools/typespec-azure-rulesets/data-plane"
options:
  "@azure-tools/typespec-autorest":
    azure-resource-provider-folder: "data-plane"
    emit-lro-options: "none"
    emitter-output-dir: "{project-root}/../"
    output-file: "data-plane/Microsoft.SchemaRegistry/{version-status}/{version}/sc\
      hemaregistry.json"
  "@typespec/http-client-python":
    package-dir: "azure-schemaregistry"
    package-name: "{package-dir}"
    emitter-output-dir: "{project-root}/azure-schemaregistry/_generated/"
    package-version: 1.3.0b4
    generate-packaging-files: false
    flavor: azure
    generate-test: true
    generate-sample: true
  "@azure-tools/typespec-python":
    package-dir: "azure-schemaregistry"
    package-name: "{package-dir}"
    emitter-output-dir: "{project-root}/azure-schemaregistry/_generated/"
    package-version: 1.3.0b4
    generate-packaging-files: false
    flavor: azure
    generate-test: true
    generate-sample: true
  "@azure-tools/typespec-java":
    package-dir: "azure-data-schemaregistry"
    namespace: com.azure.data.schemaregistry
    partial-update: true
    flavor: azure
  "@azure-tools/typespec-ts":
    package-dir: "schema-registry"
    generateMetadata: false
    generateTest: false
    packageDetails:
      name: "@azure/schema-registry"
    flavor: azure
  "@azure-tools/typespec-csharp":
    package-dir: "Azure.Data.SchemaRegistry"
    namespace: "{package-dir}"
    clear-output-folder: true
    model-namespace: true
    flavor: azure

Reproduction

1. Add the main.tsp, client.tsp, tspconfig.yaml into the project.
2. 
3. 

I'm not sure if the entrypoint file needs to be set/change elsewhere in the config files. However, I believe it should automatically use the client.tsp file as the entrypoint file/apply those if I'm explicitly right-clicking on that file for generation.

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[RodgeFu]

@timotheeguerin , @allenjzhang , do you have more context about using the client.tsp as entrypoint? I checked our doc but it only mentioned main.tsp as entrypoint.

[timotheeguerin]

typespec takes whatever input file you give it

tsp compile . // resolve the input file for the current folder which could be main.tsp or what is configured in the package.json if its there


tsp compile client.tsp // compile client.tsp
tsp compile other.tsp // compile other.tsp

if the generation is assumining its always resolving a main.tsp and not building the file that the user asked this is broken then

[chunyu3]

hello @swathipil The default entrypoint file is main.tsp, if the default entrypoint exists in the tsp project folder, Code Generation will generate code from the entrypoint file.

you can set client.tsp as your entrypoine file in package.json

"tspMain": "client.tsp"

[timotheeguerin]

This is not an good solution. The spec repo has a single package.json that should be touched and hundreds of specs.
Requiring modifying a file as well to do that completely defeats the point of having any IDE experience for his. You would be better of just running the cli.

[chunyu3]

In typespec extension, when customer select a tsp file to generate, there will be two options:

• Option 1: Generate code from the tsp file selected
• Option 2: search out the MainEntrypointTspFile( main.tsp by default), and generate code from the mainEntrypointTspFile

Option 1 more convenience, but as for a tsp project, the generated code may not acceptable if the selected file is not mainEntrypointTspFile.

typespec extension choose Option 2, make sure every round of generation generate code for the whole project.

In spec repo, it may not be suitable.

[RodgeFu]

@swathipil , i saw you have both main.tsp and client.tsp in your project. May I know more about your user scenario with these two files? When will you try to compile from main.tsp and when from client.tsp? will you need to use both of them at the same time, so have to switch frequently? thanks.

[timotheeguerin]

This is the current pattern in the azure specs repos. Main contains the service definition and client contains the client overrides. So to generate client you use client. For openapi you use main.
Ideally we’ll move away from needing this separation and have client be imported in main but there is still some incompatible things

[RodgeFu]

Ideally we’ll move away from needing this separation and have client be imported in main but there is still some incompatible things

@timotheeguerin , thanks for the details. Will it happen soon for client to be imported by main? If true, then I think we can just wait for that. Otherwise, I am thinking maybe we should do something to support that user experience in vscode considering azure specs repos is one of our major customers.

[timotheeguerin]

Will it happen soon for client to be imported by main?

this has been a idea for a long time so wouldn't count on it being resolved anytime soon.