Skip to content

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

@eric-milles

Description

@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).

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions