Parinfer is confused when functions are indirectly referenced

[simongray]

In our organisation's code base we have code taking the form:

(('foo bar) :foobar)

where the first form ('foo bar) is an indirect reference that resolves to a function and the second form :foobar is an argument to that function.

If we try to insert a newline (= press enter) between the first form and the second form, the parinfer implementation will move the parenthesis:

(('foo bar 
  :foobar))

Suddenly, :foobar is made a part of the first form.

If we then manually correct it to this (the only way possible without parinfer moving it inside the first form)

(('foo bar) 
 :foobar)

then using the automatic code formatting will put it back in the erroneous state again.

[Azzurite]

This is probably because of the styleguide stating that function arguments on new lines should be indented with only one space.

In my Cursive Parinfer, one space produces

(('foo bar) 
 :foobar)

while two spaces produces

(('foo bar 
  :foobar))

[simongray]

@Azzurite Sure, I get why it is happening. The issue is that automatic code formatting will break it no matter how its formatted, so even if I wanted to circumvent it by using a single space, any subsequent event that triggers IntelliJ's code formatting will silently break the code (e.g. local refactoring or explicitly triggering the code formatting action).

Automatic reformatting should not break existing code, only prettify it. That's a bug in my opinion.

[cursive-ghost]

This is fixed for the next EAP build. Cursive will now indent any forms where the head form is some kind of braced form (lists, vectors, maps) with one space.