Do not carry over friendly name with model is or op is

[timotheeguerin]

fix #2276 As the design for a dedicated @instanceName was not approved due to the concern that we should maybe have a more generic @name decorator that handle template I am just fixing this very anyoing carry over that requires using @friendlyName in all derived models when it is used upstream.

This is technically a breaking change as if you used to have

@friendlyName("Abc{T}", T)
model Foo<T> {}

model Bar is Foo<string>

it would have created a model called Abcstring instead of Bar

[azure-sdk]

All changed packages have been documented.

• ✅ @typespec/compiler

Show changes

@typespec/compiler - breaking ✏️

Do not carry over @friendlyName with model is or op is,> ,> tsp,> @friendlyName("Abc{T}", T),> model Foo<T> {},> ,> model Bar is Foo<string>;,> ,> // This can be changed to,> model Abcstring is Foo<string>;,>

[azure-sdk]

You can try these changes at https://cadlplayground.z22.web.core.windows.net/prs/3793/

Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/prs/3793/

[markcowl]

I think we need to see a PR against typespec-next to verify the scope and make any needed fixes.

[timotheeguerin]

I think we need to see a PR against typespec-next to verify the scope and make any needed fixes.

PR checking the changes Azure/azure-rest-api-specs#29827

There is only 2 spec impacted(and some others which could now remove the workaround this previously required).

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	📚 Next docs