We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remaining issues that should be done after TCGC supports, TCGC dependency issue is listed in each issue.
Sdkpackage adoption issue: #2665 SdkType adoption issue: #2564
Sdkpackage
SdkType
The content you are editing has changed. Please copy your edits and refresh the page.
onClient
sdkMethod
SdkServiceMethod
SdkHttpOperation
SdkMethodParameter
SdkPathParameter | SdkQueryParameter | SdkHeaderParameter | SdkBodyParameter
api-version
onClient===true
0
SdkConstantType
lroMetadata.pollingStep.responseBody.usage
The text was updated successfully, but these errors were encountered:
TCGC usage and access case study: https://gist.github.com/haolingdong-msft/df3f25a048baf83d8fabf5206aacc7db TCGC usage and access case study for spread cases: https://gist.github.com/haolingdong-msft/2d941f452551a6f96e141adbc38ac483
Sorry, something went wrong.
haolingdong-msft
No branches or pull requests
Sdkpackage
adoption issue: #2665SdkType
adoption issue: #2564Tasks
onClient
#2920sdkMethod
is overloaded #2932SdkServiceMethod
rather thanSdkHttpOperation
to generate method signature #2984TCGC dependencies
SdkMethodParameter
toSdkPathParameter | SdkQueryParameter | SdkHeaderParameter | SdkBodyParameter
? typespec-azure#1441api-version
parameter should not beonClient===true
if the server is non-versioned typespec-azure#1391TCGC dependencies for adopting access and usage
0
for model when it is only used in protocol method's response body typespec-azure#1748SdkConstantType
typespec-azure#1747lroMetadata.pollingStep.responseBody.usage
is not correct when polling operation is defined in different namespace typespec-azure#1752The text was updated successfully, but these errors were encountered: