-
Notifications
You must be signed in to change notification settings - Fork 10
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
Error: "Creating the Fantomas Deamon failed" when saving a file or trying to format in VS #54
Comments
Hmm. Just realized the path it's showing, and that in my case the Not sure why there's a 6.2 installed in the root dir, and globally, and a 5.0.6 installed in this repo. I'll fix that. This message was really confusing to me, though:
This didn't mean that it was found. It meant that there was a manifest file and that in the manifest file, it found a certain version. However, the tool was never installed in this particular directory on this machine for some reason. If you feel like it, maybe change the above to "Attempting to find Fantomas Tool as specified in the manifest file"? Or something like that? Sorry for the mess above, I was looking in the wrong direction lol... |
Whoops, my bad. |
Ehm, that's where this currently is, no? 😆 I'll have a look around and see if I can make a few changes that make reasoning about these errors easier and/or fix it such that it finds Fantomas if it's a level up or globally available. There's also the issue with |
Abel, I can't repro this. I'll reach out to you on Slack. |
In VS 2022, 17.8.0, with Fantomas 6.2.0 installed both locally (
dotnet tool restore
) and globally (the commandfantomas
is available anywhere), I get the following:Note the odd thing that it says
Found at: FantomasToolFould
and thenFantomasVersion "5.0.6"
, which is NOT a version I have installed, as far as I know:I'm not sure what's happening here. If I had to guess, maybe the tool expects a non-6.x version and should be updated for 6.x?
I can help, just need to figure out how to debug this ;).
The text was updated successfully, but these errors were encountered: