Lastly, whilst Fantomas is opinionated it also contains a number of switches that you can use to tweak how it behaves if necessary, with the documentation on the GitHub repository providing full details on the available settings.
The screenshot below illustrates a single file that has been run against Fantomas in VS Code the old version on the left and the reformatted version on the right.įantomas also includes support for working in a CI/CD setting by being able to fail if the code it checks does not conform to the standard - so you can enforce adoption of the tool without manually needing to check code, and you can retrospectively apply Fantomas formatting to an entire folder so it's a breeze to upgrade an entire project at once (or to try it out to see what things would look like). For example, in VS Code once you've installed the tool as above, your can use the standard Format Document command to execute Fantomas, or even turn on the "Format On Save" setting (which can be set at the repository level) so that every time you save your file, Fantomas will automatically reformat it.
There's also integrated tooling support for the main three IDEs (VS Code, Visual Studio and Rider). To use that, install the fantomas-tool NuGet package instead of fantomas. If you prefer to have repository-level configuration, use the following commands: dotnet new tool-manifest # if you are setting up this repoĭotnet tool install -local fantomas -prereleaseįantomas v5 pre-release is what the Fantomas team recommend you to start with v4 is the latest stable version. This installs the latest pre-release version of fantomas v5 machine-wide. Installing Fantomasįantomas is not difficult to install from the NuGet package: dotnet tool install -g fantomas -prerelease The second factor is the continued evolution and development of the Fantomas package, which is an F# code formatter tool. Having this in place is an important step towards bringing some level of consistency to the formatting. Firstly, there's a set of official F# Style Guidelines that's been developed along with a set of issues around this. As such, code formatters have become more and more popular over the years to the extent that some languages have them built in as a code part of the language - Elm being one example of that.į# doesn't have a built-in or pervasive code formatter, although this is starting to slowly change thanks to a few developments. On the one hand there's nothing necessarily wrong with that, but on the other hand one can make the argument that it's something that shouldn't be an issue or need any thought expended on it. There are certainly some patterns that we see most teams that we work with adopting, but in other cases there's a wide degree of variance.
Code formatting is something that - at least currently - in F# is somewhat of a subjective matter.
0 kommentar(er)
