You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be better if we could provide SdkApiVersionParameter as part of SdkParameter instead of SdkMethodParameter
In csharp (and probably some other languages), api-version is part of client parameters. However, certain service demands that we could provide api-version as method parameter so that users can override it. In that case, if we always provide api-version as method parameter, then we cannot differentiate where we should put api-version in the generated codes.
Check that this issue is about the Azure libraries for typespec. For feature request in the typespec language or core libraries file it in the TypeSpec repo
Currently we use .isApiVersion information on parameters for this. This is because api version can be query, path, header etc. So this is by design. If you have an idea, can you go ahead and reopen the issue? I'm closing it because I believe this is by design. Thanks!
Clear and concise description of the problem
api-version
is defined as metadata of the whole service, see an example: https://github.com/Azure/azure-rest-api-specs/blob/a5a01e06ffbbc0b0c945cb58fe769d19a4f93af4/specification/devcenter/DevCenter/main.tsp#L34SdkApiVersionParameter
as part ofSdkParameter
instead ofSdkMethodParameter
api-version
is part of client parameters. However, certain service demands that we could provideapi-version
as method parameter so that users can override it. In that case, if we always provideapi-version
as method parameter, then we cannot differentiate where we should putapi-version
in the generated codes.Checklist
The text was updated successfully, but these errors were encountered: