-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
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
System.Formats.Cbor: Backport MS Docs documentation to triple slash #48985
Comments
Tagging subscribers to this area: @eiriktsarpalis, @bartonjs Issue DetailsWe are working on a new documentation process plan, in which the main objective is to make triple slash comments the source of truth for documentation, instead of MS Docs: We want developers/maintainers to have an easier time maintaining the documentation for their APIs. You can use the DocsPortingTool to automate the backport process: Run the tool targeting the assembly, then submit a PR with the changes. You can find detailed instructions for the backporting process here. Area owners are free to decide if they want to address this in 6.0 or in Future.
|
FWIW all CBOR documentation has been authored via triple-slash comments and automatically ported to dotnet-api-docs. We'd probably still need to backport to account for any changes that have been made on dotnet-api-docs only. |
I tried running the backporting tool for CBOR and got the following errors:
This is after running both Debug and Release builds in dotnet/runtime. Could you take a look? |
Known issue: dotnet/api-docs-sync#36 and we just merged a fix: dotnet/api-docs-sync#40 Can you please update the tool to the latest bits and re-run it? BTW, the |
We are working on a new documentation process plan, in which the main objective is to make triple slash comments the source of truth for documentation, instead of MS Docs: We want developers/maintainers to have an easier time maintaining the documentation for their APIs.
You can use the DocsPortingTool to automate the backport process: Run the tool targeting the assembly, then submit a PR with the changes.
You can find detailed instructions for the backporting process here.
Area owners are free to decide if they want to address this in 6.0 or in Future.
The text was updated successfully, but these errors were encountered: