You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
moduleFoo =letbar=if output.Exists &¬(output.EnumerateFiles()|> Seq.isEmpty && onlyContainsFoobar output)then
Error (FooBarBazError.ErrorCase output)elseletblah=letx= y
None
{
Hi = blah
}|> Ok
Result
moduleFoo =letbar=if
output.Exists
&¬(
output.EnumerateFiles ()|> Seq.isEmpty
&& onlyContainsFoobar output
)then
Error (FooBarBazError.ErrorCase output)elseletblah=letx= y
None
{ Hi = blah }|> Ok
Problem description
The indentation of the branch looks good to me here, but enabling KeepIndentInBranch has caused the if condition's indentation to change in an offside-error-causing way.
Without KeepIndentInBranch, the body formats validly, as follows:
if
output.Exists
&¬(
output.EnumerateFiles ()|> Seq.isEmpty
&& onlyContainsFoobar output
)then
Extra information
[/] The formatted result breaks by code.
The formatted result gives compiler warnings.
I or my company would be willing to help fix this.
…ssions. (#1813)
* Apply same alternative formatting for match expression as in if expressions. Fixes#1774.
* Reuse alternative expression formatting with KeepIndentInBranch. Fixes#1812.
Issue created from fantomas-online
Code
Result
Problem description
The indentation of the branch looks good to me here, but enabling KeepIndentInBranch has caused the
if
condition's indentation to change in an offside-error-causing way.Without KeepIndentInBranch, the body formats validly, as follows:
Extra information
Options
Fantomas Master at 07/05/2021 06:55:07 - f4e8286
Did you know that you can ignore files when formatting from fantomas-tool or the FAKE targets by using a .fantomasignore file?
The text was updated successfully, but these errors were encountered: