Wrong indentation on multi line if/then/else expression about nixpkgs-fmt

[DavHau]

Or maybe it should add \n after the =:

let
  nix =
    if !buildNix then null else
    buildRacketNix;
in
{ }

In my opinion yes. Whenever a = is followed by an expression spanning multiple lines, there should always be a \n after the =. Because otherwise those lines cannot be logically aligned correctly to each other. Especially with larger expressions this is very important for readability.

Also I totally think that if/else should almost always be formatted like this:

if bool_expression1 then
  indented_child_expression1
else if bool_expression2 then
  indented_child_expression2
else
  indented_child_expression3

Then again, there is the question of how much freedom the developer should be given. There are always some special cases where an alternative format can make sense.

[r-burns]

Alternatively, maybe nixpkgs-fmt should move the trailing else to the next line before autoindenting. It appears that newline-before-else is much more common:

$ rg 'else$' | wc -l
1894

$ rg '^ *else' | wc -l
3870

Most of the cases of newline-after-else are actually because the else keyword is alone on the line.

$ rg '^ *else$' | wc -l
1193

[zimbatm]

Or maybe it should add \n after the =:

let
  nix =
    if !buildNix then null else
    buildRacketNix;
in
{ }

[zimbatm]

I agree that the current re-formatting is not ideal.