-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fantomas Integration #13
Comments
This is handled as part of LSP, shouldn’t you get it for free? |
That's the point, I must try it out first. |
OK, formatting works out of the box through LSP, but we should be able to configure it through settings so some work would be needed |
It seems I have to set initializationOptions and LanguageClient-neovim can only specify JSON files to use as the parameter, but |
Reading config is done on the FSAC side. |
So we don't have to modify the client, right? |
Actually no change was required (sorry for being late!) |
The link is broken. |
@kumkee Please see here: https://fsprojects.github.io/fantomas/docs/index.html Once you have installed and configured Fantomas, FSAC should use Fantomas as the formatter. (Currently, #66 is affecting Ionide-vim and it won't work with the latest FSAC, so please allow me to take some time to get everything ready to work for you.) |
@kumkee v0.58.0 is working for me. v0.58.{1,2,3,4} might also work, but I haven't tested. |
@kumkee I'm not very familiar with nvchad, but make sure that |
What if the same key combo works in all other languages? |
It seems that you are using null-ls for formatting and it doesn't contain Fantomas? https://github.com/kumkee/nvchad_config/blob/main/configs/null-ls.lua#L7C24-L34 |
It's funny that you asked. I've opened a feature request issue in null-ls. No one has responded. Please have a look. |
Since Ionide-vim delegates all the LSP functionalities (including formatting) to FSAC (and thus Fantomas), I guess Ionide-vim cannot help you solving the problem. I think you can either
|
No description provided.
The text was updated successfully, but these errors were encountered: