-
Notifications
You must be signed in to change notification settings - Fork 166
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
Emitter typespec-csharp crashed when operations under operation groups have same name. #4744
Comments
Looks like this is caused when we made up a name, we did not check for duplication, and now it duplicates and causes issues
|
This is because TCGC failed to give alias model a name. That alias model is used in a very complex way. See the bug I created on TCGC: Azure/typespec-azure#918 After TCGC getAllModels adoption, at runtime our emitter should not go to the branch mentioned by dapeng above. You can look a few lines above, and you'll realize that we invoke |
@Han-msft I would suggest to not use |
@archerzz is there any way to keep properties under |
@Han-msft There is discussion to unify the behavior of parameter spreading. In the future, named model is also spread as method input parameters: Azure/typespec-azure#612 The only uncertainty is when we will implement the change. |
@Han-msft would you mind if you could try the latest generator again? The issue should have been resolved. Thanks. |
@archerzz issue resolved after we switched to model for spread parameters. |
Describe the issue or request
Spec: https://github.com/Azure/azure-rest-api-specs/blob/be45b922eca7b7753e74e2074127f395223fa13e/specification/ai/Face/client.tsp
Exception: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3806374&view=logs&j=03afb3bb-7296-55ad-aa07-ceee610c73b2&t=0f320c29-1c90-5304-d2d3-c58a6bb76437&l=171
The text was updated successfully, but these errors were encountered: