Open MattCosturos opened 1 week ago
You could set keep-non-overloadable-protocol-signature
to true.
Yes that will do the trick. Thank you.
Is there a document somewhere listing all the possible flags and arguments? I reviewed this list but it doesn't contain keep-non-overloadable-protocol-signature
Describe the issue or request Autorest changed RequestContext from optional to required.
Previously, query parameters were set to null, and every request had an optional RequestContext. Now every method has a required RequestContext parameter.
Our entire codebase is calling methods WITHOUT providing a RequestContext. This change will require work to update every single auto rest call.
Swagger excerpt.
Previously generated signature
public virtual Response Assets(Guid? id = null, RequestContext context = null)
Newly generated signature
public virtual Response Assets(Guid? id, RequestContext context)
Previous command
autorest --version:3.9.3 --input-file=$1 --csharp --output-folder=$2 --use=@autorest/csharp@3.0.0-beta.20230706.1 --verbose
New command
autorest --version:3.10.3 --input-file=$1 --csharp --output-folder=$2 --use=@autorest/csharp@3.0.0-beta.20241030.1 --verbose
We ran into this problem last year, and that is why we haven't updated auto rest since July 2023.
Is there any flag we can set to make RequestContext optional again?
Full swagger file here https://smartfactory-dev.eastus2.cloudapp.azure.com/ea/api/swagger/v1/swagger.json
Logs