This pull request refactors the FSAC dll resolution and adds an experimental option to use the FSAC extensions in F# interactive. It also improves the logic for finding and passing the F# interactive parameters and fixes some terminal issues on windows. The main files affected are src/Core/LanguageService.fs, release/package.json, and src/Components/Fsi.fs.
🤖 Generated by Copilot at 0cfe72a
FSAC path tweaksenhance F# interactiveautumn of refactor
add experimental option to conveniently add --compilertool:/path/to/fsac to the FSI session.
related:
WHAT
🤖 Generated by Copilot at 0cfe72a
This pull request refactors the FSAC dll resolution and adds an experimental option to use the FSAC extensions in F# interactive. It also improves the logic for finding and passing the F# interactive parameters and fixes some terminal issues on windows. The main files affected are
src/Core/LanguageService.fs,release/package.json, andsrc/Components/Fsi.fs.🤖 Generated by Copilot at 0cfe72a
🛠️🚀♻️
WHY
FSAC is bound to ship great FSI extensions, let's make it convenient for users to add those to the FSI session.
HOW
🤖 Generated by Copilot at 0cfe72a
FSharp.fsiUsesFSACDirectoryForCompilerToolto enable loading FSAC extensions in F# interactive (link)fsiBinaryAndParametersfunction to use the new option and pass the--compilertoolargument to F# interactive with the FSAC path (link)SdkResolutionmodule toLanguageService.fsto handle locating the FSAC dll and the target framework for the current SDK (link)getOptionsfunction inLanguageService.fsby using theSdkResolutionmodule and removing duplicated logic (link, link)