Open
Description
I propose we add a way to provide a custom path for fantomas on Fantomas.Client
.
As explained on Ionide's discussion, we can't currently have an option to set a custom path for fantomas on VSCode.
Pros and Cons
Pros
The advantages of making this adjustment to Fantomas are ...
- Allows the user to freely set where fantomas is located while using VSCode
- Nix maintainers can package ionide with fantomas bundled by default (rust-analyzer is an example)
The disadvantages of making this adjustment to Fantomas are ...
- More code complexity
Affidavit (please submit!)
Please tick this by placing a cross in the box:
- I have read the Contribution Guidelines.
- I have searched both open and closed suggestions on this site and believe this is not a duplicate
Please tick all that apply:
- This is not a breaking change to Fantomas
- I or my company would be willing to help implement and/or test this
- This suggestion is part of the Microsoft style guide (please add a link to section if so)
- This suggestion is part of the G-Research style guide (please add a link to section if so)