Skip to content

ClientInitialization scenarios should include a scenario with optional parameters #3600

@JoshLove-msft

Description

@JoshLove-msft

Some languages have different behavior for optional initialization parameters as they would be added as properties to the ClientOptions. We should have a new scenario that contains optional parameters as well as a scenario that has both optional and required.

Metadata

Metadata

Assignees

Labels

lib:azure-http-specsFor issues/prs related to the @azure-tools/typespec-azure-http-specs package

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions