-
Notifications
You must be signed in to change notification settings - Fork 331
Closed
Description
Describe the bug
- While config server emitters in vscode, the default emitter-output-dir is different from client emitter. Is this expected?
"@typespec/http-server-csharp":
emitter-output-dir: "{output-dir}/{emitter-name}"
"@typespec/http-server-js":
emitter-output-dir: "{output-dir}/{emitter-name}"
-
The folder structure with the above setting doesn't look right as there are a couple of cs files in the root folder
I expect all items related to .net will be under http-server-csharp folder

-
The readme.md file that talked about the next step is a bit confusing. Shall we ask user to run C# scaffolding commands to generate some runnable code so that user could start the server?
-
I have no idea what I shall do with the generated JS server code? Seems there is no document or link that tells me the next step.
Reproduction
- In vscode, invoke the command of
TypeSpec: emit from TypeSpec - select .NET server and JS server code emitter.
- run the emitter.
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.