-
Notifications
You must be signed in to change notification settings - Fork 16
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
Allow porting Docs comments to Triple Slash in source #23
Conversation
cc @pgovind @jeffhandley @safern in case you want to take a look. |
Libraries/ToTripleSlashPorter.cs
Outdated
return; | ||
} | ||
|
||
Compilation? compilation = project.GetCompilationAsync().Result; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We still need to figure out how to get all compilations so that we get all the locations of an API for the cases where there is no an OS agnostic file for that API. Anyway, that could be done when we hit that scenario.
Add the Nuget.Frameworks package to the Tests project so that the underlying csproj consumes it without failure.
Support event, field and delegate.
Remove boilerplate message. Avoid adding ## Remarks. Fix bug preventing exception comments from being added.
25c8711
to
f5e1713
Compare
Fix nullability warnings. Obtain all projects related to all relevant symbols.
Add the Nuget.Frameworks package to the Tests project so that the underlying csproj consumes it without failure.
Support event, field and delegate.
Remove boilerplate message. Avoid adding ## Remarks. Fix bug preventing exception comments from being added.
Fix nullability warnings. Obtain all projects related to all relevant symbols.
…structor. Avoid adding CDATA to remarks.
Convert langwords.
…ug when detecting that string.
… converted to see crefs. Detect primitive types in see crefs and convert them to their simplified representation. Add unit tests to verify this.
…ocsPortingTool into TripleSlashRoslyn
This PR is covering enough cases that I think I can merge it. I added a GitHub CI action to run the unit tests and they are passing now. Pending tasks for the next PR:
|
The Libraries team wants to make triple slash comments the source of truth to simplify the documentation efforts from developers. In order to get there, we first need to bring back all the documentation we have in MS Docs into source code.
This change adds new logic that allows copying documentation contents from dotnet-api-docs xml files back into the triple slash comments trivia section of public APIs in C# code, on an assembly by assembly basis.
This is the first successful attempt.
Pending:
Future (nice to have):
To be added.
) but there is valid documentation in triple slash, and we want to make sure it gets preserved. It's rare since we have already manually ported our /// documentation to dotnet-api-docs in previous efforts.