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
The original point for this was to make sure the description for a server still gets generated, since it is a required parameter, I understand the concern though. Do you have any suggestions? I think it is important to still generate the docs somewhere, since we required users to input them.
The original point for this was to make sure the description for a server still gets generated, since it is a required parameter, I understand the concern though. Do you have any suggestions? I think it is important to still generate the docs somewhere, since we required users to input them.
I suggest we just leave it empty if @doc is not defined. Let each language team to decide what they want to generate by default.
Let me ask for suggestions in the TypeSpec channel. I'm not sure adding it to the end of client is the best either: in the example @archerzz gave, they just duplicated the documentation for the client.
Describe the bug
See this spec: https://github.com/Azure/azure-rest-api-specs/blob/2e5be0e72597c6fc8d438f20e38087d900c16427/specification/confidentialledger/Microsoft.CodeTransparency/main.tsp#L19-L25
In TCGC, the description of parameter
endpoint
isCode Transparency Service
, which is wrong. If@doc
is not defined, the description should be empty.Reproduction
Just parse the spec in the link above.
Checklist
The text was updated successfully, but these errors were encountered: