-
Notifications
You must be signed in to change notification settings - Fork 823
Description
We need to do an end-to-end sweep over what F1 Help is doing.
-
For .NET Library things like
System.String
we seem to go to the correct documentation -
For F# keywords we sort of do the right thing, e.g. F1 on "open" goes to https://msdn.microsoft.com/query/dev16.query?appId=Dev16IDEF1&l=EN-US&k=k(open_FS);k(SolutionItemsProject);k(DevLang-FSharp)&rd=true which re-routes to the F# docs. See why
-
For F# Library things (e.g.
Async
) F1 on open in VS2022 goes to https://msdn.microsoft.com/query/dev16.query?appId=Dev16IDEF1&l=EN-US&k=k(Microsoft.FSharp.Control.FSharpAsync`1);k(SolutionItemsProject);k(DevLang-FSharp)&rd=true which is the same as for keywords but with a different IDMicrosoft.FSharp.Control.FSharpAsync
1`. However the query service then resolves this to very old documentation for Visual Studio 2013.
The fix appears to be to adjust the query service so that we do this:
Microsoft.FSharp.Control.FSharpAsync`1 --> https://fsharp.github.io/fsharp-core-docs/reference/fsharp-control-fsharpasync.html
and in general like this (putting aside some issues with the `1
and so on)
Microsoft.AAA.BBB.CCC --> https://fsharp.github.io/fsharp-core-docs/reference/aaa-bbb-ccc.html
If necesary fsdocs/FSharp.Formatting can be modified to generate additional redirecting target pages
Metadata
Metadata
Assignees
Labels
Type
Projects
Status