Releases: Azure/typespec-azure
Releases · Azure/typespec-azure
@azure-tools/typespec-client-generator-core@0.57.1
Bug Fixes
- #2785 Add
@clientLocation
decorator to support moving an operation to another client or sub-client. - #2841 Fix operations missing problem after introducing
@clientLocation
. - #2815 Extend
@usage
to acceptjson
andxml
usage.@usage
now is used to add usage for type and namespace, instead of override the usage calculated by operation. Also, the serialization options will include JSON or XML info if new usage is added.
typespec-azure@0.57.0
@azure-tools/typespec-autorest
Bump dependencies
- #2667 Upgrade dependencies
Bug Fixes
- #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 correctly render as
type:file
- #2607 Fix
x-ms-identifiers
being 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
Bug Fixes
- #2734 Fix incorrect use of
templateArguments
inparameterizedNextLink
decorator. - #2670 Correct casing of
ArmResourceDeploymentScope
andAllArmResourceDeploymentScopes
values to follow camel case conventions.
@azure-tools/typespec-azure-portal-core
No changes, version bump only.
@azure-tools/typespec-azure-resource-manager
Features
- #2621 Adding a new
ExtensionResourceActionScope
. You can use it inArmProviderAction
operation template to describe an action operation for extension resource provider. - #2763 Add support for external resources #1428
Bug Fixes
- #2536 Fix the
arm-resource-operation
rule to excludeArmProviderActionAsync
andArmProviderActionSync
operations, as they are not considered resource operations. - #2691 Fix
@key
decorator resolution forx-ms-identifiers
: when@key
is applied to a property namedid
orname
, it will no longer add an identifier. - #2749 Relax constraints to allow resources that override properties of Foundations.Resource
@azure-tools/typespec-client-generator-core
No changes, version bump only.
@azure-tools/typespec-azure-rulesets@0.57.0
No changes, version bump only.
@azure-tools/typespec-autorest-canonical@0.18.0
No changes, version bump only.
@azure-tools/azure-http-specs@0.1.0-alpha.19
Features
- #2773 [azure-http-specs] unscope paging with re-injection parameters test for go
@azure-tools/typespec-client-generator-core@0.56.4
Bug Fixes
- #2796 Ignore empty
{}
definitions fromno-unnamed-types
rule
@azure-tools/typespec-client-generator-core@0.56.3
Bump dependencies
- #2667 Upgrade dependencies
Bug Fixes
- #2750 Refine API version parameter judgement with checking the service's API version enum.
- #2755 Fix
no-unnamed-types
linter warning not being applied to versioned namespaces - #2755 Fix linter perf for
@azure-tools/typespec-client-generator-core
linter warnings - #2770 Don't raise
no-unnamed-types
for nullable types - #2690 loosen requirements to link method to service params
- #2707 Fix documentation on generate-convenience-methods option.
@azure-tools/azure-http-specs@0.1.0-alpha.18
@azure-tools/typespec-azure-resource-manager@0.56.2
@azure-tools/typespec-azure-rulesets@0.56.1
Bug Fixes
- #2675 Discourage use of legacy types outside brownfield conversions