Asti
Asti
Hey @Nekroido, Sorry for the delayed reply. I suspect it could be a permissions issue. Here's the issue I'm seeing: > Fantomas.Client tried to run `dotnet tool list` but exited...
It will work if there's no tool manifest defined - with the globally installed formatter.
I've published a new version for VS22 that has much better error logging for this case. Could you please update and post your logs here. 😊
I've released 1.1.0 on the marketplace. You should be able to go Extensions > Manage Extensions > Update and install the new version. On Fri, 6 May 2022, 5:41 pm...
Sir, you are flexing your build skills. 😄 On Fri, 6 May 2022, 5:56 pm Abel Braaksma, ***@***.***> wrote: > Oh, yes, that'd work too! 😄 > > — >...
> Is it possible that if fantomas is configured for a project that it does not attempt to find the tool on the global path? Yes, this is the current...
On WSL2, if there's no local config, I can confirm that the file formats with the global tool.
This applies the minimal changes to the edit buffer. You should be able to hit undo unless you closed the file. But the diffs are line diffs. It looks like...
@nojaf Do we check after formatting if the CodeFormatter produced a valid output?
Hi @dahlia, thanks for reporting this. This was apparently added in September (https://devblogs.microsoft.com/visualstudio/now-introducing-arm64-support-for-vs-extensions/). Step 1 of the resolution: > update the [VSSDK Build Tools package](https://www.nuget.org/packages/Microsoft.VSSDK.BuildTools/) to the latest version via...