[typespec-autorest]: suggest removing namespace from the definition name in swagger

[dolauli]

Clear and concise description of the problem

The most common case occurs with Liftr-related services. The typespec-autorest tool prepends the namespace to model names when generating definition names in Swagger. For example:

"LiftrBase.MarketplaceDetails": {

However, for client emitters (such as C#, PowerShell, etc.), the namespace is ignored, for the example above, MarketplaceDetails will be used as the generated class name. This inconsistency will create significant challenges in the future when we transition from Swagger-based generation to typespec-based generation, as changes in definition (class) names will result in breaking changes.

I understand that the purpose of prepending the namespace is to avoid name conflicts. However, I propose the following approach:

Remove the namespace from the definition name and only prepend it when a name conflict is detected.

Checklist

• Follow our Code of Conduct
• Check that this issue is about the Azure libraries for typespec. For feature request in the typespec language or core libraries file it in the TypeSpec repo
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[allenjzhang]

I assume this is an issue with swagger based CLI/PSH codegen with typespec-autorest emitted swagger, and NOT the typespec native CLI/PSH emitter, correct?

[dolauli]

I assume this is an issue with swagger based CLI/PSH codegen with typespec-autorest emitted swagger, and NOT the typespec native CLI/PSH emitter, correct?

Yes. The inconsistency will cause breaking changes when we switch from swagger based codegen with autorest to typespec based codgen with emitter in the future.