groovy / groovy/groovy-eclipse
Disable relevance reduction of Closure methods and properties when object expression type is Closure
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 681
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Consider the following:
void meth(Closure closure) {
closure.|
}
When invoking content assist (Ctrl+Space) at |, the methods and properties of groovy.lang.Closure are very low in the list of proposals. This is due to very-well-known type adjustments made within org.codehaus.groovy.eclipse.codeassist.proposals.AbstractGroovyProposal.getRelevanceClass().
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in org.codehaus.groovy.eclipse.codeassist.proposals.AbstractGroovyProposal.getRelevanceClass(), using the Closure example in the issue to reproduce the content-assist ordering. Confirm that methods and properties from groovy.lang.Closure are no longer given reduced relevance when the expression type is Closure; the issue provides no test file to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100