Summary: | [content assist] Default constructor should not be proposed for anonymous types | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Srikanth Sankaran <srikanth_sankaran> | ||||
Component: | Core | Assignee: | Srikanth Sankaran <srikanth_sankaran> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | minor | ||||||
Priority: | P3 | CC: | amj87.iitr, daniel_megert, markus.kell.r, Olivier_Thomann, srikanth_sankaran | ||||
Version: | 3.5 | ||||||
Target Milestone: | 3.6 M7 | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Srikanth Sankaran
2010-03-29 01:53:59 EDT
The default constructor proposal is synthesized by the UI in org.eclipse.jdt.internal.ui.text.java.MethodDeclarationCompletionProposal.evaluateProposals(IType, String, int, int, int, Set, Collection) and is not a direct proposal from the JDT/Core CompletionEngine. Passing on to JDT/UI for comment and follow up. org.eclipse.jdt.core.CompletionContext.getEnclosingElement() returns the wrong context: instead of the anonymous source type it returns the initializer. Created attachment 163399 [details]
Patch under consideration
Ayush, please review.
Patch looks good Released in HEAD for 3.6M7 Verified for 3.6M7 using I20100425-2000 |