See the version list below for details.
dotnet tool install --global fantomless-tool --version 4.7.7-prerelease
dotnet new tool-manifest # if you are setting up this repo dotnet tool install --local fantomless-tool --version 4.7.7-prerelease
nuke :add-package fantomless-tool --version 4.7.7-prerelease
Why a fork
- The most important one is that fantomas' maintainer doesn't agree with fantomas removing unneeded parenthesis, so we're bringing this feature here.
- We also implemented a bugfix for comments misplacement that the maintainer doesn't agree with (trying to address his feedback would mean a lot more time to work on it, which we don't have).
- We don't hold any resentment about our PullRequests not being accepted; we can just create a fork and be happy (and we would love if at some point our diff is taken and this fork is not needed anymore).
- That being said, we don't understand some behaviours from fantomas' maintainer. We recognize that he does superb technical work, and has even fixed many of our issues, etc., but that doesn't, in our opinon, give him the right to keep being, at times, a complete jerk when replying to us in issues and some of our PullRequests. It's even more difficult to understand when, in this opensource world of meritocracy, we have even contributed so many fixes upstream ourselves (more than 10 PullRequests).
- Last but not least; we included a feature for generic type normalization which we found out makes fantomas (fantomless) incompatible with units of measure. As we don't use units of measure, we don't mind including this feature. But don't use fantomless if you use F#'s Units of Measure!
- Command line:
dotnet tool install -g fantomless-tool
How to use
Command line tool / API
Use this command to install Fantomless as a .NET 5 SDK global tool:
dotnet tool install -g fantomless-tool
For detailed guidelines, please read Fantomas: How to use.
FAKE build system
Fantomas can be easily integrated with FAKE build system.<br /> Check out the sample.
The resharper-fsharp uses fantomas under the hood to format the source code. No need for any additional plugins.
Using the latest version inside Rider
For technical reasons Rider cannot always use the latest version of Fantomas found on NuGet.
As a workaround you could install fantomas-tool locally with
dotnet tool install fantomas-tool and configure it as an External tool.
This will have an impact on your editing experiencing in Rider, the external change to the file by the command line application might trigger more internal logic inside Rider than necessary. It could be noticeable in regards to the default formatting experience.
Visual Studio Code
Alternatively, you can install the fantomas-fmt extension.
The F# Formatting extension sets up Fantomas as the default formatter for F# files, configurable from Visual Studio's options.
Visual Studio for Mac
Install fantomas-tool locally with
dotnet tool install fantomas-tool and configure it as an [External tool]
Try the Fantomas online.
Every once in a while an
beta version is published to https://www.nuget.org/.
Our previous MyGet feed is now deprecated.
This project aims at formatting F# source files based on a given configuration. Fantomas will ensure correct indentation and consistent spacing between elements in the source files. We assume that the source files are parsable by F# compiler before feeding into the tool. Fantomas follows two F# style guides: the F# code formatting guidelines from Microsoft by default and the G-Research F# code formatting guidelines via various settings.
The project is developed with the following use cases in mind:
Reformatting an unfamiliar code base. It gives readability when you are not the one originally writing the code. To illustrate, the following example
type Type = TyLam of Type * Type | TyVar of string | TyCon of string * Type list with override this.ToString () = match this with | TyLam (t1, t2) -> sprintf "(%s -> %s)" (t1.ToString()) (t2.ToString()) | TyVar a -> a | TyCon (s, ts) -> s
will be rewritten to
type Type = | TyLam of Type * Type | TyVar of string | TyCon of string * Type list override this.ToString() = match this with | TyLam(t1, t2) -> sprintf "(%s -> %s)" (t1.ToString()) (t2.ToString()) | TyVar a -> a | TyCon(s, ts) -> s
Converting from verbose syntax to light syntax. Feeding a source file in verbose mode, Fantomas will format it appropriately in light mode. This might be helpful for code generation since generating verbose source files is much easier. For example, this code fragment
let Multiple9x9 () = for i in 1 .. 9 do printf "\n"; for j in 1 .. 9 do let k = i * j in printf "%d x %d = %2d " i j k; done; done;; Multiple9x9 ();;
is reformulated to
let Multiple9x9() = for i in 1..9 do printf "\n" for j in 1..9 do let k = i * j printf "%d x %d = %2d " i j k Multiple9x9()
Formatting F# signatures, especially those generated by F# compiler and F# Interactive.
Why the name "Fantomas"?
There are a few reasons to choose the name as such. First, it starts with an "F" just like many other F# projects. Second, Fantomas is my favourite character in the literature. Finally, Fantomas has the same Greek root as "phantom"; coincidentally F# ASTs and formatting rules are so mysterious to be handled correctly.
See the Contribution Guidelines.
We would like to gratefully thank the following persons for their contributions.
- Eric Taucher
- Steffen Forkmann
- Jack Pappas
- Ivan Towlson
- Don Syme
- Gustavo Guerra
- Jared Parsons
- Denis Ok
- Enrico Sada
The library and tool are available under Apache 2.0 license. For more information see the License file.
|.NET||net5.0 net5.0-windows net6.0 net6.0-android net6.0-ios net6.0-maccatalyst net6.0-macos net6.0-tvos net6.0-windows|
This package has no dependencies.
* Multiline parentheses objectExpression in indexer expression. [#2176](https://github.com/fsprojects/fantomas/issues/2176)
* Blank line over SynEnumCase is restored incorrectly. [#2155](https://github.com/fsprojects/fantomas/issues/2155)
* XML Doc comments on DU cases seem to get shuffled. [#2188](https://github.com/fsprojects/fantomas/issues/2188)
* Comment after bar is lost in single case DU. [#2182](https://github.com/fsprojects/fantomas/issues/2182)