-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add formatting #13
Add formatting #13
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for contributing!
The change looks good, I look forward to not having to think how to format the code.
Question: Does the .editorconfig provided mean that Rider's auto-format will obey exactly the same rules as Fantomas CLI?
Command : string | ||
Args : string | ||
} | ||
type CodebasePrepStep = { Command : string ; Args : string } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm surprised that this is the G-Research convention. Does it always try to fit the record definition in one line if it's short-enough?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could put fsharp_max_record_width = 0
in your .editorconfig
.
This will use the long format if the length of the record is more than 0 characters.
Yes, this is that paint point I mentioned when using Rider. The command line check doesn't know about these and you get mixed results.
Even though the command line doesn't need any of those, to get the same result out of Rider you would need to add some of these. |
Thanks @nojaf 👍 |
I'd like to start contributing to this repository.
It seemed like a good start to enable formatting.
I've added a --check to ensure everybody does it.
If you accept this PR, don't squash the commits otherwise the git-blame-ignore-revs-file won't be effective anymore.