See and SeeAlso XMLDoc comments should be links/commands

[baronfel]

Currently see and seealso xmldoc are rendered as strings. We should try to render them as links to LSP commands that editors could use to show type documentations. For Ionide, for example, the Info Panel is a natural way to surface this information.

@cannorin do you have any insight into what a vim-based type documentation display might look like?

[github-actions]

🤖 This is an automated response from Repo Assist.

I've submitted a small improvement related to this issue: the (seealso) formatter in TipFormatter.fs now properly handles href links and langword entries (mirroring the existing (see) formatter), instead of treating every entry as a cref and directly accessing Attributes.[0].

Specifically:

• (seealso href="(redacted)"/) now renders as a Markdown link instead of passing the URL through extractMemberText
• (seealso href="(redacted)")Click here(/seealso) now renders as [Click here](url)
• (seealso langword="null"/) now renders as `null`

The full vision here — rendering cref entries as clickable command:fsharp.showDocumentation URIs — is more involved, as it requires encoding the full assembly/signature info. That would be a worthwhile follow-up if the Ionide info panel command accepts such URIs.

Generated by Repo Assist

To install this workflow, run gh aw add githubnext/agentics/workflows/repo-assist.md@828ac109efb43990f59475cbfce90ede5546586c. View source at https://github.com/githubnext/agentics/tree/828ac109efb43990f59475cbfce90ede5546586c/workflows/repo-assist.md.

[Krzysztof-Cieslak]

cref should be probably handled similar to how renderShowDocumentationLink from TipFormatter.fs behaves (including conditional rendering, enabled only for VSCode)