Bugzilla – Full Text Bug Listing
| Summary: | Codeassist relevance should privilege prefix match over need for qualification | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> |
| Component: | Core | Assignee: | David Audel <david_audel> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jed.anderson |
| Version: | 2.1 | ||
| Target Milestone: | 2.1 RC2 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
New value for relevance constant: RelevanceConstants.R_EXACT_NAME = 4 //previous value is 3 RelevanceConstants.R_UNQUALIFIED = 3 //previous value is 5 Fixed. Verified. |
Build 2.1RC1 In Openable, remove import statement for org.eclipse.jdt.core.*, then perform completion at the end of IJavaElement on signature of protected Openable(int type, IJavaElement parent, String name) { super(type, parent, name); } IJavaElement isn't the first proposition. It will privilege IJavaElementRequestor instead since it is inside same package. It should always list the exact match before (I wonder if it shouldn't also be more prioritary than expected type relevance).