This repository was archived by the owner on Jan 12, 2024. It is now read-only.
Format F# code with Fantomas #769
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 7 commits
December 7, 2020 15:42
bamarsha
requested review from
bettinaheim,
ScottCarda-MS,
cesarzc and
alan-geller
…ay_or_list_width = 80
This reverts commit 3820c6c.
bettinaheim
approved these changes
Dec 12, 2020
|
Thanks for setting it up! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR formats all F# code with Fantomas, using the default configuration except for a few changes. The configuration files changed are:
The rest of the files are formatting changes only.
The Fantomas repo has some instructions for editor integration if you want to run it on your code. You can also run it from the command line with:
I did encounter some bugs in Fantomas, and a few of them caused comments to be deleted after formatting. The bugs were relatively rare compared to the total amount of code that was formatted, but it's probably a good idea to double-check that everything was formatted correctly and no comments were lost.