Consider the following DSLD:
method name: "foo", type: "void", noParens: true, namedParams: [bar: String], params: [block: 'groovy.lang.Closure']
If we select the foo method from the auto-complete menu, 'bar' is initially selected in the editor as expected, but the context popup highlights the 'block' in bold:
After hitting tab, the 'block' gets selected, but 'bar' gets highlighted:
The context popup is rendered deep inside Eclipse/Java logic which is not aware of Groovy nature of a trailing closure parameter.
I would propose to "fix" the order of parameters just in the context popup, so at least switching and highlighting would work consistently with the editor, like this:
Consider the following DSLD:
method name: "foo", type: "void", noParens: true, namedParams: [bar: String], params: [block: 'groovy.lang.Closure']If we select the foo method from the auto-complete menu, 'bar' is initially selected in the editor as expected, but the context popup highlights the 'block' in bold:
After hitting tab, the 'block' gets selected, but 'bar' gets highlighted:
The context popup is rendered deep inside Eclipse/Java logic which is not aware of Groovy nature of a trailing closure parameter.
I would propose to "fix" the order of parameters just in the context popup, so at least switching and highlighting would work consistently with the editor, like this: