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

[Bug]: @azure-tools/typespec-csharp should generate Azure by default #5379

Open
4 tasks done
lmazuel opened this issue Dec 16, 2024 · 0 comments
Open
4 tasks done

[Bug]: @azure-tools/typespec-csharp should generate Azure by default #5379

lmazuel opened this issue Dec 16, 2024 · 0 comments
Assignees
Labels
bug Something isn't working emitter:client:csharp Issue for the C# client emitter: @typespec/http-client-csharp

Comments

@lmazuel
Copy link
Member

lmazuel commented Dec 16, 2024

Describe the bug

Given we have @typespec/http-client-csharp now as an explicit package, we don't need flavor anymore to select Azure.

Note that I'm not asking specifically to remove flavor, we can discuss if there is an usage for it. But the default should be Azure if we keep it, and it should silently ignore it (no failure) if we decide to skip it.

Reproduction

Starting the azure-tools emitter with no config at all, should generate Azure.

Checklist

@lmazuel lmazuel added bug Something isn't working emitter:client:csharp Issue for the C# client emitter: @typespec/http-client-csharp labels Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working emitter:client:csharp Issue for the C# client emitter: @typespec/http-client-csharp
Projects
None yet
Development

No branches or pull requests

3 participants