Chenjie Shi

Add a flag to disable conversion feature for backcomp

1

Since we want to use standardized expression for greenfield services, conversion need to introduce a flag to disable all features for backcomp.

Support custom operation in resource operation groups

1

ref [this](https://cadlplayground.z22.web.core.windows.net/cadl-azure/?c=aW1wb3J0ICJAdHlwZXNwZWMvaHR0cCI7CtIZcmVzdNUZdmVyc2lvbmluZ8wfYXp1cmUtdG9vbHMvyCstxhVjb3Jl3yvIK3Jlc291cmNlLW1hbmFnZXIiOwoKdXNpbmcgVHlwZVNwZWMuSHR0cDvQFVJlc3TRFVbpAKnIG0HEZS5Db3JlzhJSx3dNxnbdHS5Gb3VuZGF0aW9uczsKCkBhcm1Qcm92aWRlck5hbWVzcGFjZQpAc2VydmljZSh7CiAgdGl0bGU6ICJDb250b3NvyC5IdWJDbGllbnQiLAogIOcBVjogIjIwMjEtMTAtMDEtcHJldmlldyIsCn0pCkBkb2MoyEUg6ACWIMhPIOYBM21lbnQgQVBJLiIpCkB1c2VEZXBlbmRlbmN5KPYAz%2BcBJnMudjFfMF9QxnJfMSnlANpDb21tb27kAVJzxyjXRsspy1I1KQpu6AEUIE1pY3Jvc29mdC7yAQnkAUnlAN9BINIdIOgCFiIpCm1vZGVsIEVtcGxveWVlIGlzIFRyYWNrZWToAJE8yBxQcm9wZXJ0aWVzPiDkAYbGYOQBoyBvZiBlxyYiKcQbcGF0dGVybigiXlthLXpBLVowLTktXXszLDI0fSTGI2tleSgiyDbERsk6aMQIc2Vn5AF6yiNzxSDkAP46IHN0cuUChX3oAObpAMBw6QCl8QDc6gDA6wC%2FQWfyAL5hZ2U%2FOiBpbnQzMjsKySpDaXR50StjaXR5P%2BoAkMktUHJvZmls0ltAZW5jb2RlKCJiYXNlNjR1cmzFF3DGLz86IGJ5dGXkAwYgIEB2aXNpYmlsaXR5KCJyZWFkxkHFX1RoZSBzdGF0dXPEYnRoZSBsYXN0IOQA4OUDSOQCrMVWxETlA7FTdGF0xGDlAgbMFOsBRcRWzDTFY%2BUAxGHpAjLEWkBscm%2FEPHVzCmVudW3SVOUBYC4u6QLU0SEs6gEqxHXIXeQCfmJlxHrpAIdl5gD3zELbPXVw5ARIbmfFNFXHDd9tZyBkZWxldMdpRMQM2zVjcmXkAOFyZXF1ZXN0IGhhxEVlbiBhY2NlcMhFQccNLOQBXGludGVyZuQDsE%2FoAZ9zIGV4dGVuZHP3BRHLKXvkAZ5hcm3II8oby1noAuLmAtlnZXTkANxByjVSZWFk6QPHPjvkArjlAMdPcuUBJOUBC8svQ80dQXN5bmPOPuUBZ9A2UGF0Y2hTzCws8wN7xUDmAXHPQOUBemXNQcUtbGlzdEJ5yCZHcm91cM86TMUiUGFyZW501DxTdWJzY3JpcOQBN8c7xjPMGcw56gH8R2V05QNfaGlzdG9yeSBhIHNtYXJ0IGfkAIcsIHdoaWNoIGNhcHR1cmVzIGFueSBTxSDmAKfmA0BjaGFuZ2VzIChOZXcvQWNrbm93bGVkZ2VkL0Nsb3NlZCkg5gOvLy8gRklYTUU6xkTFQ3NfR2V0SMd9Y291bGQgbm90IGJlIGNvbnZlcnRlZCB0b%2BsDoOoEBAogIOQAx2dldAogIG9w5AIXx0koCiDFAS4uLuwBAklkUGFyYW1ldGVy5AdAxyJEZWZhdWx08QeS5QMhxAHmASnmAPflARcgdW5pcXVlIGlkLiDlANnFJucF2MUM6QXc5QFN5QDpSeYDOsQBzBXoBVsKKTrnAfJwb25z6gaUPiB8IEVycm9yyBrkBM8%3D&e=%40azure-tools%2Ftypespec-autorest&options=%7B%7D) this could be applied to any other operations calculated by .NET metadata, since .NET will only aggregate operations with same path prefix.

1. Deprecated: Use Azure.Core.armResourceIdentifier instead。 2. @azure-tools/typespec-azure-resource-manager/arm-resource-name-pattern: The resource name parameter should be defined with a 'pattern' restriction. Decorate the "name" property in the resource definition using the @pattern decorator,...

Be somewhat intelligent to generate `ArmTagsPatch` rather than `ArmCustomPatch` if the current update model only has Tags.

Refine ARM template usage with named templated parameters

1

``` create is ArmResourceCreateOrRepalceAsync< Employee, BaseParameter, // ; ``` => ``` create is ArmResourceCreateOrRepalceAsync< Employee, LroHeaders = ArmAsyncOperationheader>; ```

 Either add doc to show how to deal with csharp config or change csharp codegen to enhance the error handling logic.

Convert `x-ms-mutability` to visibility. Ref: https://github.com/Azure/autorest/tree/main/docs/extensions#x-ms-mutability Ref: https://typespec.io/docs/standard-library/built-in-decorators#@visibility

Current generate to `@secret`, but may loose info of visibility. It will impact client generation directly from TSP, we should revisit the implementation.

Will compile to `title` node in swagger.

1. investigate the behavior for autorest emitter about `| null` 2. add support in conversion