[generator]: do not keep a class under Azure.Core namespace even if its accessibility is internal
#4597
Assignees
Labels
Comments
archerzz
added a commit
to archerzz/autorest.csharp
that referenced
this issue
Apr 18, 2024
Even the accessibility is set, we should not keep them since they should be referenced from Azure.Core resovle Azure#4597
archerzz
added a commit
to archerzz/autorest.csharp
that referenced
this issue
Apr 18, 2024
Even the accessibility is set, we should not keep them since they should be referenced from Azure.Core resovle Azure#4597
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
communication/Communication.JobRouterhas marked some operationsinternal: https://github.com/Azure/azure-rest-api-specs/blob/c4e661cdf92c8f579574008d0cd11874cc303da0/specification/communication/Communication.JobRouter/client.tsp#L25Thus, the accessibility of some foundation models are marked as
internal.In current implementation, we'll keep a model as long as its accessibility is set. I think we should not keep any foundation model, no matter what the accessibility is. If it's really used, it should be referenced from
Azure.Core, not from our generated codes.The text was updated successfully, but these errors were encountered: