We have a test case in autorest.csharp, where the client constructors are not generated following the .NET guidelines. This has been described in this issue: https://github.com/azure/autorest.csharp/issues/2055
We need to determine how best to handle global parameters in generated client constructors. Since there are no Data Plane Generated libraries that currently have this case in their OpenAPI specs, we will not block DPG GA on this.
Success Criteria
Redmond team provides a spec indicating how to handle global parameters in generated client constructors.
Once we have determined the design we want for the generated client constructors on clients that have global parameters, we will complete work on #2055.
Note: We have had a number of discussions about this offline, and as time allows, that information will be added to this issue so that it contains the full context.
Problem
We have a test case in autorest.csharp, where the client constructors are not generated following the .NET guidelines. This has been described in this issue: https://github.com/azure/autorest.csharp/issues/2055
We need to determine how best to handle global parameters in generated client constructors. Since there are no Data Plane Generated libraries that currently have this case in their OpenAPI specs, we will not block DPG GA on this.
Success Criteria
Redmond team provides a spec indicating how to handle global parameters in generated client constructors.
Once we have determined the design we want for the generated client constructors on clients that have global parameters, we will complete work on #2055.
Note: We have had a number of discussions about this offline, and as time allows, that information will be added to this issue so that it contains the full context.