-
Notifications
You must be signed in to change notification settings - Fork 868
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
[Bug] .NET API / Markdown: Unresolved cref / xref
tags from <summary>
in generated markdown.
#9879
Comments
Currently generated markdown files with So generated markdown files contains some docfx specific custom tags like
If there are no strict requirements for previewing the markdown file on GitHub. |
@Delsin-Yu and @filzrev, I similarly ran into this with Not sure if it's intentional or a mistake? <p>
e.g.:
<code>
[](xref:System.String?title=String+Class)
</code>
will be resolved as
<a href="xref:System.String?title=String+Class"></a>.
</p> |
It seems resolved by publishing docs to GitHub pages. @Delsin-Yu |
There is a following issue when talking about resolving xrefs,, should I open a separate issue on it? Since it's not markdown-related. |
It seems be caused by #9677 issue. |
Describe the bug
The following XML Documentation:
does not resolve when converted to markdown, this is what appears in the GitHub.
In contrast, the generated website appears to resolve the links correctly:
Docfx.json
docfx.json
configSource Repo
The GDViews.VirtualGridView repo.
The text was updated successfully, but these errors were encountered: