Improve discovery of parentheses level for MethodCallExpression

[jevanlingen]

What's changed?

Parentheses discovery for method calls did not always work properly.

What's your motivation?

• Problem with parsing groovy files #4055

Failing parts:

Micronaut.build(args)
    .packages('com.edalex')
    .mainClass(Application)
    .start()

Any additional context

The discovery of parentheses is quite hard to grasp. This is the concept behind it. We defined two variables called parent and child. The parent and child are nodes, which could be visualised like: <<child> parent>. Notice in source code, the nodes could span multiple lines.

To support this, we loop through all the lines of code of the parent and child element:

for (int i = 0; i < (childLineNumber - parentLineNumber); i++)
  // move `untilCursor` past next line break every time

// move `untilCursor` after childColumn of last line

Checklist

• I've added unit tests to cover both positive and negative cases
• I've read and applied the recipe conventions and best practices
• I've used the IntelliJ IDEA auto-formatter on affected files

[timtebeek]

Nice! Really hammering out those fixes today.