DSLD method proposals with positional and optional parameters showing incorrect name-type pairings

[eric-milles]

Consider the following:

contribute(enclosingCall(name('withConfig') & hasArgument('configuration')) & inClosure() & isScript() & isThisType()) {
    method(name:'ast', type:void, params:[xform:'java.lang.Class<? extends Annotation>'], optionalParams:[attributes:Map])
}

and the script:

withConfig(configuration) {
  a|
}

Completion at | is showing proposal ast(Class attributes) in the list of proposals.

It should be showing either ast(Class xform) or ast(Map attributes, Class xform).

[eric-milles]

org.eclipse.jdt.ui.text.java.CompletionProposalLabelProvider.appendUnboundedParameterList(StyledString, CompletionProposal) gets parameter names from total list set on proposal object (includes optional params) and parameter types from method signature (does not include optional params).