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
Renamed models themselves are generated correctly, but not get propagated to all of the usages like in operations and models.
For example, in AppConfig, we renamed the model "Error" to "AppConfigError" in tsp. While in generated code, it's still using the old name as return type in some operations, like in begin_create_snapshot() (note: the return type of this method does not generate correctly, should be LRO[_models.Snapshot]) Also in models, like in model OperationDetails.
Expected:
Should generate with the new name on the renamed models in all usages in the package.
The text was updated successfully, but these errors were encountered:
@YalinLi0312 About return type of begin_create_snapshot is wrong which causes by bug of typespec-azure-core and I have created issue https://github.com/Azure/typespec-azure/issues/1407 to track it., according to Azure/typespec-azure#1407 (comment), the typespec author shall update the typespec definition.
Renamed models themselves are generated correctly, but not get propagated to all of the usages like in operations and models.
For example, in AppConfig, we renamed the model "Error" to "AppConfigError" in tsp. While in generated code, it's still using the old name as return type in some operations, like in begin_create_snapshot() (note: the return type of this method does not generate correctly, should be
LRO[_models.Snapshot]
) Also in models, like in model OperationDetails.Expected:
Should generate with the new name on the renamed models in all usages in the package.
The text was updated successfully, but these errors were encountered: