groovy / groovy/groovy-eclipse
Fully qualified type name inserted in private final field declaration instead of import + simple name (disregarding workspace preference)
Open
Nobody has claimed this yet.
bug
- Dominant language
- Java
- Stars
- 681
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Variation of #866.
Consider this class:
package test50
class Test50 {
String foo
private final TreeNode|
}
Invoke code assist at "|" and choose javax.swing.tree.TreeNode.
Once again, the fully qualified name is inserted instead of the import declaration.
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
Reproduce the issue from the Test50 example in the body by invoking code assist at the private final TreeNode declaration and choosing javax.swing.tree.TreeNode. Compare this behavior with issue #866 and the workspace preference for imports. Done means code assist inserts an import and the simple type name instead of the fully qualified name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100