-
Notifications
You must be signed in to change notification settings - Fork 40
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
give a nonredundant name for templated instance model #393
Conversation
All changed packages have been documented. |
You can try these changes at https://cadlplayground.z22.web.core.windows.net/typespec-azure/prs/393/ Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/typespec-azure/prs/393/ |
"OperationState", | ||
"Error", | ||
"InnerError", | ||
"ExportedUser", | ||
"ErrorResponse", | ||
"OperationStatus", | ||
"OperationStatusExportedUserError", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i believe these are both core models, correct?
nit: I don't think we should modify the names of core models based off of templating. Not the biggest issue though, bc ideally no one should be generating with core models. If it makes the code much harder, no need to change your existing code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIK, OperationStatus
is exported in Java and .NET. I don't think this will only happen for core model. This will happen when implicitly using templated model without @friendlyName
in templated operation. And it is a possible usage for customer. Since .NET and Java need this nonredundant naming insurance, I prefer to add it in TCGC.
resolve: #334