You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Link #1538 (comment), create a seperate issue to make it more clear.
Issue
For below example, LroOperationStatus model is initial response, and should not be generated. But TCGC will return the model with name LroOperationStatusError and 'public' access, thus after adopting TCGC's access, this model will be generated, which is incorrect.
I personally do not think so.
TCGC should not make assumptions how a SDK generator would use those models related with an operation.
A generator could decide to generate the initial response as part of its API, and this model is really one of the possible return types of this operation.
Therefore from TCGC's perspective, this is by design and correct.
If TCGC keeps the current usage and access for LRO intial response, we should have a way to let emitter know when to update access and do not generate this model. But this will make TCGC's access less helpful as emitter still need to update it based on usage.
/cc @ArcturusZhang@tadelesh
Link #1538 (comment), create a seperate issue to make it more clear.
Issue
For below example,
LroOperationStatus
model is initial response, and should not be generated. But TCGC will return the model with nameLroOperationStatusError
and 'public' access, thus after adopting TCGC's access, this model will be generated, which is incorrect.Solution
TCGC returns usage
0
to indicate the model should not be generated.The text was updated successfully, but these errors were encountered: