0.57.0
TypeSpec Core 1.1 See changes to the TypeSpec language and core libraries
Features
Section titled “Features”@azure-tools/typespec-azure-resource-manager
Section titled “@azure-tools/typespec-azure-resource-manager”- #2621 Adding a new
ExtensionResourceActionScope. You can use it inArmProviderActionoperation template to describe an action operation for extension resource provider. - #2763 Add support for external resources #1428
Bug Fixes
Section titled “Bug Fixes”@azure-tools/typespec-autorest
Section titled “@azure-tools/typespec-autorest”- #2762 Emits all path parameters as required even if optional in TypeSpec. Reports a new warning if an optional path parameter is found:
@azure-tools/typespec-autorest/unsupported-optional-path-param. - #2756 Fix
HttpPart<File>correctly render astype:file - #2607 Fix
x-ms-identifiersbeing automatically populated, which caused default values to be overwritten unexpectedly. Now, it is only set when explicitly defined. - #2775 Models used to construct a multipart body will not be omitted from the definitions
@azure-tools/typespec-azure-core
Section titled “@azure-tools/typespec-azure-core”- #2734 Fix incorrect use of
templateArgumentsinparameterizedNextLinkdecorator. - #2670 Correct casing of
ArmResourceDeploymentScopeandAllArmResourceDeploymentScopesvalues to follow camel case conventions.
@azure-tools/typespec-azure-resource-manager
Section titled “@azure-tools/typespec-azure-resource-manager”- #2536 Fix the
arm-resource-operationrule to excludeArmProviderActionAsyncandArmProviderActionSyncoperations, as they are not considered resource operations. - #2691 Fix
@keydecorator resolution forx-ms-identifiers: when@keyis applied to a property namedidorname, it will no longer add an identifier. - #2749 Relax constraints to allow resources that override properties of Foundations.Resource