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
I have yet to find any related links in standard .NET cmdlets that are not links to other PowerShell topics, but at least XmlDoc2CmdletDoc provides support for standard web links as well. The issue, though, is just the output rendering. Say you have two links, one a web link and one a plain link:
/// <para type="link" uri="http://tempuri.org">My Web Page</para>
/// <para type="link">about_Gizmos</para>
They will render as:
My Web Page http://tempuri.org
about_Gizmos
The web link is technically correct but hard to visually discern the parts. It would be easier on the user--as well as allow for easier post-processing should the occasion arise--if the output was in standard markdown format, clearly delineating what is attached to the link:
[My Web Page](http://tempuri.org)
about_Gizmos
My recommendation then is: if the link is recognized as a weblink in GetCommandRelatedLinksElement() then output it in markdown format as shown; otherwise output it "as is".
The text was updated successfully, but these errors were encountered:
I have yet to find any related links in standard .NET cmdlets that are not links to other PowerShell topics, but at least XmlDoc2CmdletDoc provides support for standard web links as well. The issue, though, is just the output rendering. Say you have two links, one a web link and one a plain link:
They will render as:
The web link is technically correct but hard to visually discern the parts. It would be easier on the user--as well as allow for easier post-processing should the occasion arise--if the output was in standard markdown format, clearly delineating what is attached to the link:
My recommendation then is: if the link is recognized as a weblink in GetCommandRelatedLinksElement() then output it in markdown format as shown; otherwise output it "as is".
The text was updated successfully, but these errors were encountered: