Option to add XRef link is missing

[pmaytak]

Option to add Xref link using Alt + M > Link .

VS Code:
Version: 1.88.1 (system setup)
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
Date: 2024-04-10T17:41:02.734Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22631

Name: Learn Authoring Pack
Version: 1.0.1

Name: learn-markdown
Version: 1.0.7

[pmaytak]

Downgrading learn-markdown extension to 1.0.3 fixed this - link to XRef is there again.

[meganbradley]

@pmaytak The underlying Xref service is being retired so this was removed from the current version by design.

[pmaytak]

@meganbradley Does this mean all the current xref links in the docs will stop working and will need to be updated? Or is this only related to the VS Code plugin? If the xref links will still work, can a doc page be added giving examples of how to properly use the xref syntax? Thanks.

[mikeebowen]

@meganbradley, I use this feature quite a lot. Is there any replacement or guidance on what to do with the feature removed?

[guardrex]

We could use some help with this, too, on the ASP.NET Core docs repo. We were using a couple of tools that we hand-built in ASP.NET Core (websites that we were running in Azure), but our tools are broken now due to churn in the API docs web API. I was just trying to revert back over to using the Learn Markdown extension's Link to XREF feature. Now, that's gone.

I'll take it up internally to see what management wants us to do, but I hope our only option isn't having to go back to looking at the ms.assetid <meta> tag of API doc files. That's CrAzY 😵 slow ... and thus expensive and costly to Microsoft 💸💸💸.

Note: I tried the advice above of downgrading the extension. Yes, that brings back the command. However, it doesn't work, probably for the same reason that our custom tools broke ... the API docs underlying web API service is different now. It broke us, and it has probably broken that old Link to XREF command code.