Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[tsp init] Azure project should be initiated with a tspconfig file with options for client code generation #1842

Open
4 tasks done
josefree opened this issue Nov 12, 2024 · 1 comment · May be fixed by #1977
Open
4 tasks done
Assignees

Comments

@josefree
Copy link
Member

Clear and concise description of the problem

suggest to improve the TypeSpec project templates for Azure. New Azure service can start from "tsp init https://aka.ms/typespec/azure-init" to scaffolding their TypeSpec project. Currently, after initializing, the tspconfig.yaml has only autorest configuration. The expectation is that it should be initialized with typespec- configurations too, referring to azure-rest-api-specs/specification/contosowidgetmanager/Contoso.Management/tspconfig.yaml at main · Azure/azure-rest-api-specs ('contoso' should be replaced by the namespace specified by user in responding to the question "Please provide ARM Resource Provider Name in Pascal case". see screenshot below.).

Image

Checklist

  • Follow our Code of Conduct
  • Check that this issue is about the Azure libraries for typespec. For feature request in the typespec language or core libraries file it in the TypeSpec repo
  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
@maririos
Copy link
Member

I believe this is the same as issue I recently opened: Azure/azure-sdk-tools#9382

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants