Bugzilla – Full Text Bug Listing
| Summary: | [1.7][content assist] constructor proposal if type not yet imported should appear before type proposals | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> |
| Component: | Text | Assignee: | JDT-Text-Inbox <jdt-text-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, eclipse, jjohnstn, mauromol |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
>a) make constructor completion also work for not imported types
This works, but the proposal's relevance is too low so that the types are coming before the constructor proposal.
What I find really annoying when working with Java7 code is that the constructor completion is always made with the type arguments (independently whether these types and the generic type are already imported or not), so that the result is immediately marked with a warning of "Redundant specification of type arguments". Should this deserve a new enhancement request (or does any already exist?). This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This still applies to Eclipse 2019-12 - and it's quite annoying ;-) (In reply to Mauro Molinari from comment #4) > This still applies to Eclipse 2019-12 - and it's quite annoying ;-) But it no longer applies to Eclipse 2020-03 RC1: https://www.eclipse.org/downloads/packages/release/2020-03/rc1 You're right, I just tried 2020-03 RC-1 and it seems like it's fixed! A small but yet very appreciated enhancement! :-) This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. Working as of 2020-03 RC1 |
BETA_JAVA7 Content assist for constructor invocation should also allow to use diamond if the type is not yet imported. Example: package p; import java.util.List; import java.util.Map; public class Customer { public static void main(String[] args) { Map<String, List<Customer>> map= new Hash } } Content assist after "new Hash" completes to "new HashMap<String, List<Customer>>". This is the same as in 3.7. But with Java 7, it would better complete to "new HashMap<>". In both cases, the result is still not really satisfying, since there are no more proposals after the type has been completed and the import added. Better solutions: a) make constructor completion also work for not imported types b) in this case, just add the import and insert "HashMap" without any type arguments, so that the user can just press Ctrl+Space again