Closed nojaf closed 10 months ago
Still found a minor issue: https://github.com/fsprojects/fantomas/issues/2806
Thanks so much - this is definitely highly desired - the stroustrup style makes life a lot easier, particularly in the Arm
namespace because we make heavy use of nested list comprehensions, and without stroustrup it pushes everything across more and more.
Thanks for confirming, I'll get back to you later this week once we have fixed the found issue.
Would also be great to have fsharp_newline_before_multiline_computation_expression = true
set as well.
(As an aside, isn't the setting named backwards? Surely it should be false for e.g
let x = foo {
bar 123
}
Yeah, naming is hard 😅.
fsharp_newline_before_multiline_computation_expression = true
by default. See https://fsprojects.github.io/fantomas/docs/end-users/Configuration.html#fsharp_newline_before_multiline_computation_expression
What we are going for:
There will be a newline before the computation expression by default.
let something = // Here is the newline before the computation expression
task {
let! thing = otherThing ()
return 5
}
If you don't want the CE to go to the next line (aka you don't want the newline):
let something = (* no newline before the CE *) task {
let! thing = otherThing ()
return 5
}
So, you want the setting to be false
?
Hi @nojaf - can we look at getting the conflicts dealt with? Thanks
@martinbryant done!
Amazing @nojaf thanks :)
Since we don't have any active PRs right now, I recommend we get this merged as soon as possible.
@nojaf can you please resolve the conflicts one more time?
Or should this use fantomas 6.2.0 instead of 6.1.2 @nojaf ?
You can check out the version differences at https://github.com/fsprojects/fantomas/blob/main/CHANGELOG.md.
I'll go ahead and close this PR. Whether this gets merged or not doesn't really matter to me anymore. If someone else ever wants to do the upgrade, they can use this PR as a reference. 😊
The changes in this PR are as follows:
I have read the contributing guidelines and have completed the following:
Hi there,
We are trying to get some in-the-field feedback on our next major release. If memory serves correctly someone was interested in the Stroustrup style for Farmer as it could be a good fit when there is a lot of configuration. I could be wrong and this was more about when using Farmer versus the actual Farmer codebase. V6 has made a lot of improvements in that area, so I'm curious to hear your thoughts.