ClientInitialization scenarios should include a scenario with optional parameters
Open
lib:azure-http-specs
- Dominant language
- TypeScript
- Stars
- 27
- Forks
- 90
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 156
Description
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.
Contributor guide
Assessment
This issue has not been assessed yet.