1. support action template
2. add suppression for
"@azure-tools/typespec-azure-core/composition-over-inheritance"
3. add suppression for
"@azure-tools/typespec-azure-resource-manager/arm-resource-provisioning-state"
---------
Co-authored-by: Pan Shao <pashao@microsoft.com>
1. Upgrade tsp compiler to 0.61
2. Fix paging response issues by:
2.1 if user customize the paging response then use the customized mode.
2.2 if user defined model is the same as ResourceListResult, then
replace it by ResourceListResult
2.3 if interface name conflicts with model name, then rename interface
name
3. Support customize LRO
4. Support ArmProviderActionAsync template.
---------
Co-authored-by: Pan Shao <pashao@microsoft.com>
1. Fix the incorrect encoded name.
2. Remove hardcoded operationid for ArmResourceListByParent
3. Some query parameters and baseParmaetes are not generated correctly.
Fixed in this PR.
4. Uptake the operationid linter to
@azure-tools/typespec-azure-core/no-openapi
5. Upgrade compiler version to 0.60
6. @operationId are added to operations in routes.tsp in accordance with
its original one.
7. Add suppressions to enums without documents.
---------
Co-authored-by: Pan Shao <pashao@microsoft.com>
1. update ruleset in tspconfig.yaml
2. Some operations are not calculated as resource operations
3. Some duplicate operations in the same interface
4. interface Operations extends Azure.ResourceManager.Operations should
be generated according to swagger
5. Take variables into consideration when calculating parent.
---------
Co-authored-by: Pan Shao <pashao@microsoft.com>
Fix https://github.com/Azure/autorest/issues/4995
What still left is:
1. Multi path cases depend on TypeSpec design: "arm-apimanagement",
"arm-compute", "arm-machinelearningservices"
2. Expanded cases depend on TypeSpec design: "arm-dns"
3. Deal with directives: an example is arm-storage.
---------
Co-authored-by: Pan Shao <pashao@microsoft.com>
Upgrade tsp version of converter to 0.58
Uptake changes from
- https://github.com/Azure/typespec-azure/issues/709
1. For brownfield: add flag `arm-resource-flattening`, add
`@@flattenProperty` to properties if needed, direct use of
Azure.ResourceManager.XXXResource allows us not need
`x-ms-client-flatten` any more.
2. For greenfield: no flag `arm-resource-flattening`, no
`@@flattenProperty`
- https://github.com/Azure/typespec-azure/issues/862
Remove all the workaround for Azure.ResourceManager.XXXResource.
---------
Co-authored-by: Pan Shao <pashao@microsoft.com>
1. Fix https://github.com/Azure/autorest/issues/4963
2. Support "x-ms-identifiers"
3. Add #suppress
"@azure-tools/typespec-azure-resource-manager/arm-resource-provisioning-state"
on the enum for provisioning.
1. Fix#4953
2. Change the logic of isFullCompatible to "only brownfield is full
compatible"
3. Add compiler server to vscode setting
4. Enable "arm-agrifood", "arm-sphere", "arm-test"
Pan Shao
Timothee Guerin
Mike Harder
Patrick Hallisey
Joel Hendrix
Wes Haggard
Jose Manuel Heredia Hidalgo
Laurent Mazuel
Rodge Fu
Chenjie Shi
Gil LaHaye