Decorators
Azure.ClientGenerator.Core
Section titled “Azure.ClientGenerator.Core”@access
Section titled “@access”Override access for operations, models, enums and model properties.
When setting access for namespaces,
the access info will be propagated to the models and operations defined in the namespace.
If the model has an access override, the model override takes precedence.
When setting access for an operation,
it will influence the access info for models/enums that are used by this operation.
Models/enums that are used in any operations with @access(Access.public)
will be set to access “public”
Models/enums that are only used in operations with @access(Access.internal)
will be set to access “internal”.
The access info for models will be propagated to models’ properties,
parent models, discriminated sub models.
The override access should not be narrower than the access calculated by operation,
and different override access should not conflict with each other,
otherwise a warning will be added to the diagnostics list.
Model property’s access will default to public unless there is an override.
@Azure.ClientGenerator.Core.access(value: EnumMember, scope?: valueof string)
The target type you want to override access info.
ModelProperty | Model | Operation | Enum | Union | Namespace
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
value | EnumMember | The access info you want to set for this model or operation. It should be one of the Access enum values, either Access.public or Access.internal . |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Set access
Section titled “Set access”@access(Access.internal)model ModelToHide { prop: string;}// Access.internal@access(Access.internal)op test: void;
Access propagation
Section titled “Access propagation”@discriminator("kind")model Fish { age: int32;}
// Access.internal@discriminator("sharktype")model Shark extends Fish { kind: "shark"; origin: Origin;}
// Access.internalmodel Salmon extends Fish { kind: "salmon";}
// Access.internalmodel SawShark extends Shark { sharktype: "saw";}
// Access.internalmodel Origin { country: string; city: string; manufacture: string;}
// Access.internal@get@access(Access.internal)op getModel(): Fish;
Access influence from operation
Section titled “Access influence from operation”model Test1 {}
// Access.internal@access(Access.internal)@route("/func1")op func1(@body body: Test1): void;
// Access.publicmodel Test2 {}
// Access.public@route("/func2")op func2(@body body: Test2): void;
// Access.publicmodel Test3 {}
// Access.public@access(Access.public)@route("/func3")op func3(@body body: Test3): void;
// Access.publicmodel Test4 {}
// Access.internal@access(Access.internal)@route("/func4")op func4(@body body: Test4): void;
// Access.public@route("/func5")op func5(@body body: Test4): void;
// Access.publicmodel Test5 {}
// Access.internal@access(Access.internal)@route("/func6")op func6(@body body: Test5): void;
// Access.public@route("/func7")op func7(@body body: Test5): void;
// Access.public@access(Access.public)@route("/func8")op func8(@body body: Test5): void;
@alternateType
Section titled “@alternateType”Set an alternate type for a model property, Scalar, or function parameter. Note that @encode
will be overridden by the one defined in the alternate type.
When the source type is Scalar
, the alternate type must be Scalar
.
@Azure.ClientGenerator.Core.alternateType(alternate: unknown, scope?: valueof string)
The source type to which the alternate type will be applied.
ModelProperty | Scalar
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
alternate | unknown | The alternate type to apply to the target. |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Change a model property to a different type
Section titled “Change a model property to a different type”model Foo { date: utcDateTime;}@@alternateType(Foo.date, string);
Change a Scalar type to a different type
Section titled “Change a Scalar type to a different type”scalar storageDateTime extends utcDateTime;@@alternateType(storageDateTime, string, "python");
Change a function parameter to a different type
Section titled “Change a function parameter to a different type”op test(@param @alternateType(string) date: utcDateTime): void;
Change a model property to a different type with language specific alternate type
Section titled “Change a model property to a different type with language specific alternate type”model Test { @alternateType(unknown) thumbprint?: string;
@alternateType(AzureLocation[], "csharp") locations: string[];}
@apiVersion
Section titled “@apiVersion”Specify whether a parameter is an API version parameter or not.
By default, we detect an API version parameter by matching the parameter name with api-version
or apiversion
, or if the type is referenced by the @versioned
decorator.
Since API versions are a client parameter, we will also elevate this parameter up onto the client.
This decorator allows you to explicitly specify whether a parameter should be treated as an API version parameter or not.
@Azure.ClientGenerator.Core.apiVersion(value?: valueof boolean, scope?: valueof string)
The target parameter that you want to mark as an API version parameter.
ModelProperty
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
value | valueof boolean | If true, we will treat this parameter as an api-version parameter. If false, we will not. Default is true. |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Mark a parameter as an API version parameter
Section titled “Mark a parameter as an API version parameter”namespace Contoso;
op test( @apiVersion @header("x-ms-version") version: string,): void;
Mark a parameter as not presenting an API version parameter
Section titled “Mark a parameter as not presenting an API version parameter”namespace Contoso;op test( @apiVersion(false) @query api-version: string): void;
@client
Section titled “@client”Define the client generated in the client SDK.
If there is any @client
definition or @operationGroup
definition, then each @client
is a root client and each @operationGroup
is a sub client with hierarchy.
This decorator cannot be used along with @clientLocation
. This decorator cannot be used as augmentation.
@Azure.ClientGenerator.Core.client(options?: Azure.ClientGenerator.Core.ClientOptions, scope?: valueof string)
The target namespace or interface that you want to define as a client.
Namespace | Interface
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
options | ClientOptions | Optional configuration for the service. |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Basic client definition
Section titled “Basic client definition”namespace MyService {
}
@client({ service: MyService,})interface MyInterface {}
Changing client name
Section titled “Changing client name”namespace MyService {
}
@client({ service: MyService, name: "MySpecialClient",})interface MyInterface {}
@clientApiVersions
Section titled “@clientApiVersions”Specify additional API versions that the client can support. These versions should include those defined by the service’s versioning configuration. This decorator is useful for extending the API version enum exposed by the client. It is particularly beneficial when generating a complete API version enum without requiring the entire specification to be annotated with versioning decorators, as the generation process does not depend on versioning details.
@Azure.ClientGenerator.Core.clientApiVersions(value: Enum, scope?: valueof string)
The target client for which you want to define additional API versions.
Namespace
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
value | Enum | If true, we will treat this parameter as an api-version parameter. If false, we will not. Default is true. |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Add additional API versions to a client
Section titled “Add additional API versions to a client”@versioned(Versions)namespace Contoso { enum Versions { v4, v5, }}
// client.tsp
enum ClientApiVersions { v1, v2, v3, ...Contoso.Versions,}
@@clientApiVersions(Contoso, ClientApiVersions);
@clientDoc
Section titled “@clientDoc”Override documentation for a type in client libraries. This allows you to provide client-specific documentation that differs from the original documentation.
@Azure.ClientGenerator.Core.clientDoc(documentation: valueof string, mode: EnumMember, scope?: valueof string)
The target type (operation, model, enum, etc.) for which you want to apply client-specific documentation.
unknown
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
documentation | valueof string | The client-specific documentation to apply |
mode | EnumMember | Specifies how to apply the documentation (append or replace) |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Replacing documentation
Section titled “Replacing documentation”@doc("This is service documentation")@clientDoc("This is client-specific documentation", DocumentationMode.replace)op myOperation(): void;
Appending documentation
Section titled “Appending documentation”@doc("This is service documentation.")@clientDoc("This additional note is for client libraries only.", DocumentationMode.append)model MyModel { prop: string;}
Language-specific documentation
Section titled “Language-specific documentation”@doc("This is service documentation")@clientDoc("Python-specific documentation", DocumentationMode.replace, "python")@clientDoc("JavaScript-specific documentation", DocumentationMode.replace, "javascript")op myOperation(): void;
@clientInitialization
Section titled “@clientInitialization”Allows customization of how clients are initialized in the generated SDK.
By default, the root client is initialized independently, while sub clients are initialized through their parent client.
Initialization parameters typically include endpoint, credential, and API version.
With @clientInitialization
decorator, you can elevate operation level parameters to client level, and set how the client is initialized.
This decorator can be combined with @paramAlias
decorator to change the parameter name in client initialization.
@Azure.ClientGenerator.Core.clientInitialization(options: Azure.ClientGenerator.Core.ClientInitializationOptions, scope?: valueof string)
The target client that you want to customize client initialization for.
Namespace | Interface
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
options | ClientInitializationOptions | The options for client initialization. You can use ClientInitializationOptions model to set the options. |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Add client initialization parameters
Section titled “Add client initialization parameters”namespace MyService;
op upload(blobName: string): void;op download(blobName: string): void;
// client.tspnamespace MyCustomizations;model MyServiceClientOptions { blobName: string;}
@@clientInitialization(MyService, {parameters: MyServiceClientOptions})// The generated client will have `blobName` in its initialization method. We will also// elevate the existing `blobName` parameter from method level to client level.
@clientLocation
Section titled “@clientLocation”Change the operation location in the client. If the target client is not defined, use string
to indicate a new client name.
This decorator allows you to change the client an operation belongs to in the client SDK.
This decorator cannot be used along with @client
or @operationGroup
decorators.
@Azure.ClientGenerator.Core.clientLocation(target: Interface | Namespace | valueof string, scope?: valueof string)
The operation to change location for.
Operation
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
target | Interface | Namespace | valueof string | The target Namespace , Interface or a string which can indicate the client. |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Move to existing sub client
Section titled “Move to existing sub client”@servicenamespace MoveToExistingSubClient;
interface UserOperations { @route("/user") @get getUser(): void;
@route("/user") @delete @clientLocation(AdminOperations) deleteUser(): void; // This operation will be moved to AdminOperations sub client.}
interface AdminOperations { @route("/admin") @get getAdminInfo(): void;}
Move to new sub client
Section titled “Move to new sub client”@servicenamespace MoveToNewSubClient;
interface ProductOperations { @route("/products") @get listProducts(): void;
@route("/products/archive") @post @clientLocation("ArchiveOperations") archiveProduct(): void; // This operation will be moved to a new sub client named ArchiveOperations.}
Move operation to root client
Section titled “Move operation to root client”@servicenamespace MoveToRootClient;
interface ResourceOperations { @route("/resource") @get getResource(): void;
@route("/health") @get @clientLocation(MoveToRootClient) getHealthStatus(): void; // This operation will be moved to the root client of MoveToRootClient namespace.}
@clientName
Section titled “@clientName”Changes the name of a client, method, parameter, union, model, enum, model property, etc. generated in the client SDK.
@Azure.ClientGenerator.Core.clientName(rename: valueof string, scope?: valueof string)
The type you want to rename.
unknown
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
rename | valueof string | The rename you want applied to the object. |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Rename a model
Section titled “Rename a model”@clientName("RenamedModel")model TestModel { prop: string;}
Rename a model property
Section titled “Rename a model property”model TestModel { @clientName("renamedProp") prop: string;}
Rename a parameter
Section titled “Rename a parameter”op example(@clientName("renamedParameter") parameter: string): void;
Rename an operation
Section titled “Rename an operation”@clientName("nameInClient")op example(): void;
Rename an operation for different language emitters
Section titled “Rename an operation for different language emitters”@clientName("nameForJava", "java")@clientName("name_for_python", "python")@clientName("nameForCsharp", "csharp")@clientName("nameForJavascript", "javascript")op example(): void;
@clientNamespace
Section titled “@clientNamespace”Changes the namespace of a client, model, enum or union generated in the client SDK. By default, the client namespace for them will follow the TypeSpec namespace.
@Azure.ClientGenerator.Core.clientNamespace(rename: valueof string, scope?: valueof string)
The type you want to change the namespace for.
Namespace | Interface | Model | Enum | Union
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
rename | valueof string | The rename you want applied to the object |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Change a namespace to a different name
Section titled “Change a namespace to a different name”@clientNamespace("ContosoClient")namespace Contoso;
Move a model to a different namespace
Section titled “Move a model to a different namespace”@clientNamespace("ContosoClient.Models")model Test { prop: string;}
@convenientAPI
Section titled “@convenientAPI”Whether you want to generate an operation as a convenient method.
@Azure.ClientGenerator.Core.convenientAPI(flag?: valueof boolean, scope?: valueof string)
The target operation.
Operation
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
flag | valueof boolean | Whether to generate the operation as a convenience method or not. |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”@convenientAPI(false)op test: void;
@deserializeEmptyStringAsNull
Section titled “@deserializeEmptyStringAsNull”Indicates that a model property of type string
or a Scalar
type derived from string
should be deserialized as null
when its value is an empty string (""
).
@Azure.ClientGenerator.Core.deserializeEmptyStringAsNull(scope?: valueof string)
The target type that you want to apply this deserialization behavior to.
ModelProperty
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”model MyModel { scalar stringlike extends string;
@deserializeEmptyStringAsNull prop: string;
@deserializeEmptyStringAsNull prop: stringlike;}
@flattenProperty
Section titled “@flattenProperty”Set whether a model property should be flattened or not. This decorator is not recommended to use for green field services.
@Azure.ClientGenerator.Core.flattenProperty(scope?: valueof string)
The target model property that you want to flatten.
ModelProperty
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”model Foo { @flattenProperty prop: Bar;}model Bar {}
@operationGroup
Section titled “@operationGroup”Define the sub client generated in the client SDK.
If there is any @client
definition or @operationGroup
definition, then each @client
is a root client and each @operationGroup
is a sub client with hierarchy.
This decorator cannot be used along with @clientLocation
. This decorator cannot be used as augmentation.
@Azure.ClientGenerator.Core.operationGroup(scope?: valueof string)
The target namespace or interface that you want to define as a sub client.
Namespace | Interface
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”@operationGroupinterface MyInterface {}
@override
Section titled “@override”Customize a method’s signature in the generated client SDK. Currently, only parameter signature customization is supported. This decorator allows you to specify a different method signature for the client SDK than the original definition.
@Azure.ClientGenerator.Core.override(override: Operation, scope?: valueof string)
: The target operation that you want to override.
Operation
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
override | Operation | : The override method definition that specifies the exact client method you want |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Customize parameters into an option bag
Section titled “Customize parameters into an option bag”@servicenamespace MyService;
op myOperation(foo: string, bar: string): void; // by default, we generate the method signature as `op myOperation(foo: string, bar: string)`;
// client.tspnamespace MyCustomizations;
model Params { foo: string; bar: string;}
op myOperationCustomization(params: MyService.Params): void;
@@override(MyService.myOperation, myOperationCustomization); // method signature is now `op myOperation(params: Params)`
Customize a parameter to be required
Section titled “Customize a parameter to be required”@servicenamespace MyService;
op myOperation(foo: string, bar?: string): void; // by default, we generate the method signature as `op myOperation(foo: string, bar?: string)`;
// client.tspnamespace MyCustomizations;
op myOperationCustomization(foo: string, bar: string): void;
@@override(MyService.myOperation, myOperationCustomization)
// method signature is now `op myOperation(params: Params)` just for csharp // method signature is now `op myOperation(foo: string, bar: string)`
@paramAlias
Section titled “@paramAlias”Alias the name of a client parameter to a different name. This permits you to have a different name for the parameter in client initialization and the original parameter in the operation.
@Azure.ClientGenerator.Core.paramAlias(paramAlias: valueof string, scope?: valueof string)
The target model property that you want to alias.
ModelProperty
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
paramAlias | valueof string | The alias name you want to apply to the target model property. |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Elevate an operation parameter to client level and alias it to a different name
Section titled “Elevate an operation parameter to client level and alias it to a different name”namespace MyService;
op upload(blobName: string): void;
// client.tspnamespace MyCustomizations;model MyServiceClientOptions { blob: string;}
@@clientInitialization(MyService, MyServiceClientOptions)@@paramAlias(MyServiceClientOptions.blob, "blobName")
// The generated client will have `blobName` in it. We will also// elevate the existing `blob` parameter to the client level.
@protocolAPI
Section titled “@protocolAPI”Whether you want to generate an operation as a protocol method.
@Azure.ClientGenerator.Core.protocolAPI(flag?: valueof boolean, scope?: valueof string)
The target operation.
Operation
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
flag | valueof boolean | Whether to generate the operation as a protocol method or not. |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”@protocolAPI(false)op test: void;
@responseAsBool
Section titled “@responseAsBool”Indicates that a HEAD operation should be modeled as Responsefalse
.
2xx will return true
. Everything else will still raise an error.
@Azure.ClientGenerator.Core.responseAsBool(scope?: valueof string)
The target operation that you want to apply this behavior to.
Operation
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”@responseAsBool@headop headOperation(): void;
Define the scope of an operation. By default, the operation will be applied to all language emitters. This decorator allows you to omit the operation from certain languages or apply it to specific languages.
@Azure.ClientGenerator.Core.scope(scope?: valueof string)
The target operation that you want to scope.
Operation
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Omit an operation from a specific language
Section titled “Omit an operation from a specific language”@scope("!csharp")op test: void;
Apply an operation to specific languages
Section titled “Apply an operation to specific languages”@scope("go")op test: void;
Add usage for models/enums.
A model/enum’s default usage info is always calculated by the operations that use it.
You can use this decorator to add additional usage info.
When setting usage for namespaces,
the usage info will be propagated to the models defined in the namespace.
If the model has a usage override, the model override takes precedence.
For example, with operation definition op test(): OutputModel
,
the model OutputModel
has default usage Usage.output
.
After adding decorator @@usage(OutputModel, Usage.input | Usage.json)
,
the final usage result for OutputModel
is Usage.input | Usage.output | Usage.json
.
The usage info for models will be propagated to models’ properties,
parent models, discriminated sub models.
@Azure.ClientGenerator.Core.usage(value: EnumMember | Union, scope?: valueof string)
The target type you want to extend usage.
Model | Enum | Union | Namespace
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
value | EnumMember | Union | The usage info you want to add for this model. It can be a single value of Usage enum value or a combination of Usage enum values using bitwise OR.For example, Usage.input | Usage.output | Usage.json . |
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”Add usage for model
Section titled “Add usage for model”op test(): OutputModel;
// The resolved usage for `OutputModel` is `Usage.input | Usage.output | Usage.json`@usage(Usage.input | Usage.json)model OutputModel { prop: string;}
Propagation of usage, all usage will be propagated to the parent model, discriminated sub models, and model properties.
Section titled “Propagation of usage, all usage will be propagated to the parent model, discriminated sub models, and model properties.”// The resolved usage for `Fish` is `Usage.input | Usage.output | Usage.json`@discriminator("kind")model Fish { age: int32;}
// The resolved usage for `Shark` is `Usage.input | Usage.output | Usage.json`@discriminator("sharktype")@usage(Usage.input | Usage.json)model Shark extends Fish { kind: "shark"; origin: Origin;}
// The resolved usage for `Salmon` is `Usage.output | Usage.json`model Salmon extends Fish { kind: "salmon";}
// The resolved usage for `SawShark` is `Usage.input | Usage.output | Usage.json`model SawShark extends Shark { sharktype: "saw";}
// The resolved usage for `Origin` is `Usage.input | Usage.output | Usage.json`model Origin { country: string; city: string; manufacture: string;}
@getop getModel(): Fish;
@useSystemTextJsonConverter
Section titled “@useSystemTextJsonConverter”Whether a model needs the custom JSON converter, this is only used for backward compatibility for csharp.
@Azure.ClientGenerator.Core.useSystemTextJsonConverter(scope?: valueof string)
The target model that you want to set the custom JSON converter.
Model
Parameters
Section titled “Parameters”Name | Type | Description |
---|---|---|
scope | valueof string | Specifies the target language emitters that the decorator should apply. If not set, the decorator will be applied to all language emitters by default. You can use ”!” to exclude specific languages, for example: !(java, python) or !java, !python. |
Examples
Section titled “Examples”@useSystemTextJsonConvertermodel MyModel { prop: string;}