#1097 incoming call hierarchy

[TheAngryByrd]

Definitely need a parsing/typed expert here.

• Outgoing calls
  • I was able to use references and top level navigation items, but that comes with missing fidelity into nested expressions.
• Incoming calls
  • Ranges aren't right but I wanted to get something up
  • Needed the type tree here to get function/method calls but that causes keepAssemblyContents to need to be set to true in the FSharpChecker (losing enablePartialTypeChecking in the process since they're mutually exclusive).

---

WHAT

🤖 Generated by Copilot at c68553f

This pull request enhances the F# language server by adding the call hierarchy feature and by refactoring the file management logic. It modifies the AdaptiveFSharpLspServer type to keep track of both open and closed files and to use this information for various language features. It also updates the Common.fs file to enable the CallHierarchyProvider capability.

🤖 Generated by Copilot at c68553f

CallHierarchyProvider Enhances language server Autumn of refactor

📞♻️🔎

WHY

HOW

🤖 Generated by Copilot at c68553f

• Refactor the AdaptiveFSharpLspServer type to store and update information about both open and closed F# files in the workspace, and to simplify the logic of getting the project options, parsed results, and declarations for any file path. (link, link, link, link, link, link, link)
• Implement the CallHierarchyIncomingCalls and TextDocumentPrepareCallHierarchy methods in the AdaptiveFSharpLspServer type to provide the functionality of finding the callers and callees of a given symbol in the workspace, using the existing parsing, type checking, and symbol use logic. (link)
• Modify the workspaceSymbol function in the AdaptiveFSharpLspServer type to use the new function getAllDeclarations instead of the old function getAllOpenDeclarations, to improve the accuracy of the workspace symbol search feature. (link)
• Add the CallHierarchyProvider capability to the Helpers module in the Common.fs file, to enable the language server to advertise its support for the call hierarchy feature to the LSP client. (link)
• Remove an empty line from the code in the AdaptiveFSharpLspServer type, likely as a formatting or style adjustment. (link)

[TheAngryByrd]

I confess that I have a hard time reasoning about the 'directions' (incoming/outgoing) and matching them to the FCS calls going on here.

Incoming is like walking the call tree back to its roots. (So a recursive fine all references essentially).

Outgoing is like walking the call tree to its leaves. (So a recursive find all functions called).

I might actually punt on the Outgoing for the moment because it isn’t really possible without the typed tree (as far as I can tell), As that disables partial type checking.

[TheAngryByrd]

• IncomingCalls is pretty much completed. I could add more tests here.
• I removed OutgoingCalls because of what I outlined previously. Unless there's something I've missed, I don't think it's an easy fix.
• I was bad and did some extra work here (can move to own branch if necessary)
  • I cleaned up AdaptiveExtensions a bit
  • I added a Version to DiagnosticCollection. We occasionally get TextSync issues, while I think there's something else going on, I think stopping it at the DiagnosticCollection will stop it from being a problem.