-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Net10 docs update #11847
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
Net10 docs update #11847
Conversation
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.
WCF api's look good
We're down to just 3 warnings in the build:
Tensor instances were added
I suspect we need to fix up that cross-reference. I'll see if I can determine what it should be. The |
This looks like it might be a bug, because the DocId in the inheritdoc seems to match the DocId in the method exactly. |
Yeah I found the same. I'm not sure why the build is claiming it doesn't match. Can we see if there's some consequence of this warning in the generated docs? I could just remove that reference in order to avoid the warning. Just for my information -- what value does |
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
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.
Reviewed through WeakGCHandle.
xml/System.Runtime.CompilerServices/UnsafeAccessorTypeAttribute.xml
Outdated
Show resolved
Hide resolved
xml/System.Runtime.InteropServices.Java/ComponentCrossReference.xml
Outdated
Show resolved
Hide resolved
I've added this case to an existing internal work item for inheritdoc doc IDs.
I don't see inheritdoc in the HTML, but it remains in the XML in dotnet-api-docs. |
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.
GitHub has pretty much ground to a halt when I make suggestions now (it does that as the number of suggestions grows) so I'll commit my remaining review suggestions directly.
xml/System.Threading.Tasks.Sources/ManualResetValueTaskSourceCore`1.xml
Outdated
Show resolved
Hide resolved
The fixup of incorrectly escaped I think I was able to apply all feedback. I had to use VS code and apply somewhat manually in a few cases due to line number changes. |
This is probably a bug in api-docs-sync that should be fixed. |
1567bb8
to
95de27f
Compare
I found the problem. It's actually misinterpreting other syntax as a markdown link due to use of [](): https://github.com/dotnet/runtime/blob/925205d06d82ce5e0d24e4e313fd66887fe89795/src/libraries/System.Private.CoreLib/src/System/Runtime/Intrinsics/Arm/Sve.cs#L92
I'll undo the change I made and try to get it to render this correctly. |
I opened dotnet/api-docs-sync#180 to track the other mangling of para tags that we saw in this. |
This is looking better. |
@gewarren let me know once you're done looking at this and I will merge. After that we need another intellisense build, ingest that into 10.0, then another undocumented API report, and file the issues. |
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.
LGTM
Porting .NET 10.0 intellisense
I had to workaround a few issues I filed.
I also noticed a net change to the repo without any new docs input (simply changes the tool did on its own) - which has also been divided as it's own commit 02f539e
Please look through each and check off when done.
Changes by only running PortToDocs w/o new API 02f539e