Having an empty multiline set as the last parameter in an application in a set puts it on an extra line
That title should describe it… sorry for the length of it.
Given this input:
{
test = app {
};
}
I would expect the expression not to be reformatted at all. The current master version however returns:
{
test =
app
{
};
}
Interestingly enough, having a non-expanded second argument prevents this from happening, resulting in:
{
test = app {
} { };
}
It does however also happen if I start with two already-expanded attrsets as the parameters:
{
test =
app
{
}
{
};
}
That looks like a regression, could you maybe bisect it?
First time I see this is 23b4c1f51cd7ea2f32912b09f070a43afe63aefd. In the previous commit (aff0520720cf913523d6e3a45dd7df8a1b2516fa), we have the old contraction logic which causes the entire file to be put into a single line.